Replies: 5 comments 12 replies
-
|
what version of mod_auth_openidc are you on? |
Beta Was this translation helpful? Give feedback.
-
|
upgrading to a recent release should solve this issue then: it will check for a "sub" claim |
Beta Was this translation helpful? Give feedback.
-
|
seems to be 2.4.5 |
Beta Was this translation helpful? Give feedback.
-
|
No longer seeing the 401 embedded response on refresh but now the userinfo is being completly omitted on refresh.
|
Beta Was this translation helpful? Give feedback.
-
|
@zandbelt Do you have an idea of when this will make it into a full release? I'm just wanting to set expectations internally. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
We have
mod_auth_openidcimplemented at scale with a shared redis cache. Everything has been working great until our IdP vendor updated their userinfo endpoint to return401on expiredaccess_tokeninstead of403. We now are seeing odd behavior at end of session. Theaccess_tokenis getting refreshed but the userinfo is returned as an embedded401. My theory is that the new status code is causing the error response to be cached.Beta Was this translation helpful? Give feedback.
All reactions