Skip to content

Conversation

kennethklee
Copy link
Contributor

@kennethklee kennethklee commented Jul 2, 2025

Fixes #105

The forward auth endpoint correctly returns 2xx status code for authenticated requests. However, it returns 401 instead of triggering login from saml.

Changes:

  • adds RequreAccount middleware to auth verify path endpoint

@kennethklee kennethklee changed the title fix: requires auth to forward auth handler (uthVerify flag) fix: requires auth to forward auth handler (AuthVerify config) Jul 2, 2025
Copy link
Owner

@itzg itzg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Likewise I'm not sure now when that broke.

@itzg itzg added the bug Something isn't working label Jul 2, 2025
@itzg itzg merged commit 348e1e7 into itzg:master Jul 2, 2025
2 checks passed
@itzg
Copy link
Owner

itzg commented Jul 2, 2025

Released in https://github.com/itzg/saml-auth-proxy/releases/tag/1.17.2

@kennethklee kennethklee deleted the fix/forward-auth branch July 2, 2025 16:55
@itzg
Copy link
Owner

itzg commented Jul 21, 2025

Now that I see #109 I remember why it used to done in the original code. I think it's going to turn out that these two behaviors need to be a configurable choice.

@itzg
Copy link
Owner

itzg commented Jul 22, 2025

@kennethklee can you also review the latest changes in

https://github.com/itzg/saml-auth-proxy/pull/109/files

@kennethklee
Copy link
Contributor Author

makes sense. lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Forward auth doesn't redirect to saml login
2 participants