Hy all,

I apologize for my French English.

I have a problem when I upgrade my CAS 5.2.x to CAS 5.3.7 with the SAML 
delegation.
My Cas 5.3.7 is configure to use the OpenIdConnect authentication but it is 
possible to delegate the authentication to an IDP SAML2.
I have no problem with the delegation in CAS 5.2.x 

When I use the OIDC authentication without delegation, the workflow is 
correct.
Workflow:
1 The user enter its password and login in the authentication page
2 The user is redirect to a consent page
3 When click on the button "allow", an authorization code is returned

But when I use the SAML2 delegation, I am not redirect to the consent page:
1 The user click on the button which redirect to the correct IDP
2 The user logged on the IDP SAML  
3 After the user is returned to my CAS 5.3.7 and arrived on the page 
service?ticket=ST-x 
<https://idp-auth.poc-mobilite.test-gar.education.fr/com.worldline.bcmc.gar.openidcpoc.oidcnongar:/oauthredirect?ticket=ST-4-3XKBx3tGziyH-T3nCMxlmedrnycidp-auth.poc-mobilite.test-gar.education.fr>xxxxxxxxxxxxxxxxxxxxxxxxxxx
 
and I have a code 302


I found this issue in the github which seems to correspond to my 
problem https://github.com/apereo/cas/pull/3664.
It describe the same issue in CAS 5.3.x in the SAML2 protocol before the 
bug was fixed. It didn't concern the delegation.
Could it be this problem is related to my issue?

Thanks for any help.

Kyra

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/266a8093-f4d3-4ffa-bfea-1d071d595933%40apereo.org.

Reply via email to