-
-
Notifications
You must be signed in to change notification settings - Fork 327
Replies: 2 comments · 17 replies
-
presumably you are using |
Beta Was this translation helpful? Give feedback.
All reactions
-
I appear to be having this exact problem. I can confirm I'm using Require Claim iss: inside my directory directive. I can't get the metadata directory to work, but switching to a single provider with metadata URL works fine. |
Beta Was this translation helpful? Give feedback.
All reactions
-
which version are you using? |
Beta Was this translation helpful? Give feedback.
All reactions
-
FWIW, on a different note: the Require statements need to be on different lines to be effective |
Beta Was this translation helpful? Give feedback.
All reactions
-
I guess in our deployment apache acts as reverse proxy (we have to use it specifically in order to use OIDC) that passes on request with empty user field to our internal backend (envoy) resulting in 401 instead of expected redirect to discovery page. This only started happening with upgrade from 2.4.4 to later version. so when I hit start page /v3 I get this on logs:
I worked around this by explicit redirect to discovery page if incoming request does not have mod_auth_openidc_session cookie set (meaning user is not yet authorized)
|
Beta Was this translation helpful? Give feedback.
All reactions
-
You have:
but in the configs that you sent I cannot find any |
Beta Was this translation helpful? Give feedback.
All reactions
-
I just verified what I sent you is correct.
So, not sure where it comes from. I was surprised to see that, too. For comparison, when I used plugin 2.4.4 the log with all same configs looked like this:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
I'm starting to see the issue here: it is the mod_auth_form that is conflicting with mod_auth_openidc here and the former actually returns deny in the authorization phase after mod_auth_openidc has interacted with the request. In the end this is a matter of two authentication modules trying to be first: your workaround is probably your best chance, if you need a code fix you'll have to work on a PR yourself or get into a commercial development agreement via [email protected]. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
I'm using Fedora 34 and since I upgraded mod_auth_openidc from 2.4.8.4 to 2.4.9, OIDCMetadataDir has stopped working.
A new message appears
which appears to be related to ac56864 48ad854 d6a9361
But even with the latest version that message is still there.
Beta Was this translation helpful? Give feedback.
All reactions