Projet

Général

Profil

Bug #51248

lasso_init after lasso_shutdown results in empty issuer errors

Ajouté par Jürn Brodersen il y a environ 3 ans. Mis à jour il y a environ 3 ans.

Statut:
Rejeté
Priorité:
Normal
Assigné à:
-
Catégorie:
-
Version cible:
-
Début:
18 février 2021
Echéance:
% réalisé:

0%

Temps estimé:
Patch proposed:
Oui
Planning:
Non

Description

Hi,

in case lasso_shutdown is called and the lasso lib is later initialized
again with lasso_init , lasso_node_impl_init_from_xml fails.

This happens because the lasso default registry is cleared on shutdown
but not the static this_type variable from
lasso_saml2_name_id_get_type, as a consequence the Issuer mapping is
not added to the registry again and lasso_node_impl_init_from_xml
fails due to the missing mapping.

Always adding the mapping to the registry seems to work fine. I attached a proposed patch for this.
I also attached a patch to test lasso after lasso_shutdown was called once.

Thank you very much!


Fichiers

Historique

#1

Mis à jour par Benjamin Dauvergne il y a environ 3 ans

  • Statut changé de Nouveau à Rejeté

It's just not possible to initialize lasso after a shutdown, do not try to do that many things will not work, when Lasso is initialized it should be used until the end of the process, lasso_shutdown has no use anymore; it's the same as with GLib/GObject you cannot shutdown it anymore.

#2

Mis à jour par Jürn Brodersen il y a environ 3 ans

Benjamin Dauvergne a écrit :

It's just not possible to initialize lasso after a shutdown, do not try to do that many things will not work, when Lasso is initialized it should be used until the end of the process, lasso_shutdown has no use anymore; it's the same as with GLib/GObject you cannot shutdown it anymore.

Thank you for your answer, we shall adapt our code.

Formats disponibles : Atom PDF