-
Hi there, I'm having an issue where we have a "Require claim group:" statement that is failing and returning 401 even though we can pretty clearly see that the is present in the debug logs. I feel like we are missing something very simple that would explain this. If we comment out the "Require claim group:" statement, we can successfully load the page. See the relevant apache config below:
And the log lines that include the
I've also tried modifying the
Are there any other configuration attributes that could help us troubleshoot this issue? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
which version of mod_auth_openidc are you on? |
Beta Was this translation helpful? Give feedback.
-
Hi zandbelt@, thanks for the quick response. Using
|
Beta Was this translation helpful? Give feedback.
-
Also, upon some more investigation, I can see with a different setup, it looks like we should expect to see this
but in the instance described in the OP, it looks like it is only evaluating "sub" for some reason even though it seems to be successfully setting the headers/env variables for all of the claims (not just sub) |
Beta Was this translation helpful? Give feedback.
-
well 1.8.5 is almost 9 years old..., the problem could be anything; I suggest upgrading to the latest 2.4.15.7 most likely you're running into #120 |
Beta Was this translation helpful? Give feedback.
-
thanks hans, you are correct, it looks like the issue was #120. due to some legacy issues (separate problem), the most recent version available from the system package manager was 1.8.5. we have upgraded to 1.8.10 and can confirm by grepping the debug logs that all of the id_token claim keys are being evaluated we will have to revisit the major version upgrade to 2.4.x i'll mark this discussion as closed, thank you for the support, it is much appreciated! |
Beta Was this translation helpful? Give feedback.
well 1.8.5 is almost 9 years old..., the problem could be anything; I suggest upgrading to the latest 2.4.15.7
most likely you're running into #120