Support #26617

ServerProviderNotFoundError in SP using python-lasso 2.5.0 with Authentic2 server using python-lasso 2.5.1

Ajouté par Alexandre Allouche il y a 3 mois. Mis à jour il y a 5 jours.

Statut:Information nécessaireDébut:21 sept. 2018
Priorité:NormalEchéance:
Assigné à:Alexandre Allouche% réalisé:

0%

Catégorie:-
Version cible:-
Patch proposed:Non

Description

This might be misleading but using an upgraded python-authentic2 package 2.1.37 with a python service provider which used to work fine, I encounter a ServerProviderNotFoundError when processing the final auth response.

Here is the code in the SP
https://github.com/xcgd/server-auth/blob/10.0/auth_saml/models/res_users.py#L72

I don't know if it comes from a difference in minor versions of Lasso.
Hopefully this is just a glitch somewhere in the config but I don't have any clue at the moment.
I couldn't catch any useful info from the debug log in Authentic2 where everything seems fine (sso treatment ended, send response)

Any idea?

Historique

#1 Mis à jour par Alexandre Allouche il y a 3 mois

By the way, is it expected that 2.1.37 is running on django 1.8?

#2 Mis à jour par Benjamin Dauvergne il y a environ 2 mois

Alexandre Allouche a écrit :

By the way, is it expected that 2.1.37 is running on django 1.8?

Yes.

#3 Mis à jour par Alexandre Allouche il y a environ 2 mois

Any idea about the main error or hiw to collect further information for debug?

I have both OIDC and SAML2.0 activated in this instance. Is there any known conflict? OIDC manages external account creation and later authentication with additionnal attributes. SAMLv2 is used to authenticate internal users in another SP.

#5 Mis à jour par Mikaël Ates il y a 5 jours

  • Assigné à mis à Alexandre Allouche
  • Statut changé de Nouveau à Information nécessaire
  • Quelle version de lasso ?
  • Rapporter login.server.debug() au moment de l'exception
  • Rapporter login.debug() au moment de l'exception
  • Rapporter token au moment de l'exception

Formats disponibles : Atom PDF