Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RA - Error on invalid token #418

Open
phavekes opened this issue Nov 30, 2024 · 5 comments
Open

RA - Error on invalid token #418

phavekes opened this issue Nov 30, 2024 · 5 comments

Comments

@phavekes
Copy link
Member

This issue is imported from pivotal - Originaly created at Sep 6, 2024 by Peter Havekes

When the user has no token with a sufficient level to enter the RA portal, the error
"Error - Not authorised to sign in
You are not authorised to sign in"
was shown. After the php8 update the error displayed is :
Authentication failure: An authentication exception occurred.: "Failed SAMLResponse parsing"

@phavekes phavekes self-assigned this Nov 30, 2024
@phavekes
Copy link
Member Author

Foutmelding voor upgrade (Peter Havekes - Sep 6, 2024)

@phavekes
Copy link
Member Author

Foutmelding na uiograde
(Peter Havekes - Sep 6, 2024)

@phavekes
Copy link
Member Author

I scoped this out. The SAML bundle Authentication FailureHandler (vendor/surfnet/stepup-saml-bundle/src/Security/Authentication/Handler/FailureHandler.php) is responsible for this new behavior.

It now returns a Http Response object containing te html described in the bug report.

What might help in fixing this issue is to create a custom FailureHandler that reproduces the previous behavior. And that returns a (Redirect)Response to the regular error route. (Michiel Kodde - Sep 11, 2024)

@phavekes
Copy link
Member Author

@phavekes 

I'm having trouble reproducing this.
What I did:
I changed \Surfnet\SamlBundle\Security\Authentication\Handler\ProcessSamlAuthenticationHandler to always throw throw new AuthenticationException(\'Failed SAMLResponse parsing\', 0, new \RuntimeException(\'Erreur\'));
But it always shows this screen:

I also tried running my local checkout in prod mode, but the result is the same.

But, now I see, based on the timestamps, that @michielkodde has probably already fixed this: 319e682

I even reviewed it #332 🙈 (Johan Kromhout - Oct 31, 2024)

@phavekes
Copy link
Member Author

This was already solved in 319e682
(Peter Havekes - Oct 31, 2024)

@phavekes phavekes removed their assignment Nov 30, 2024
@phavekes phavekes added the ra label Dec 3, 2024
@phavekes phavekes transferred this issue from OpenConext/Stepup-Project Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New
Development

No branches or pull requests

1 participant