Project

General

Profile

Support #26617

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

Added by Alexandre Allouche 9 months ago. Updated 7 months ago.

Status:
Information nécessaire
Priority:
Normal
Category:
-
Target version:
-
Start date:
21 Sep 2018
Due date:
% Done:

0%

Patch proposed:
No
Planning:
No

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?

History

#1 Updated by Alexandre Allouche 9 months ago

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

#2 Updated by Benjamin Dauvergne 8 months ago

Alexandre Allouche a écrit :

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

Yes.

#3 Updated by Alexandre Allouche 8 months ago

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 Updated by Mikaël Ates 7 months ago

  • Assignee set to Alexandre Allouche
  • Status changed from Nouveau to 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

Also available in: Atom PDF