OpenID compliance check is not based on the final specification #10987
-
Describe the bugHello 👋🏼 [1] [2] https://openid.net/specs/openid-connect-session-1_0.html [3] https://openid.net/specs/openid-connect-session-1_0-17.html Reproduction steps
Expected behaviorThis check should not be part of the compliance check. Additional contextFor anyone else having the same issue with 3.13.x, you can still manually enable that endpoint discovery following this documentation EDIT: Any reason why the previous one got delete ? https://github.com/rabbitmq/rabbitmq-server/issues/10969 |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
@elythh there is a very specific reason why it was deleted: it was moved to a discussed and answered #10972 (comment). |
Beta Was this translation helpful? Give feedback.
-
I don't have anything to add to #10972 (comment). Unless this becomes problematic for paying users, there are no plans to change anything besides adding a doc note to the Auth0 example. This is not an issue for other identity providers either. Our team does not use issues for discussions => this will be locked. |
Beta Was this translation helpful? Give feedback.
-
FTR, we have encountered a similar complaint from a paying user and here is the current (very brief) change plan: #11067. |
Beta Was this translation helpful? Give feedback.
I don't have anything to add to #10972 (comment). Unless this becomes problematic for paying users, there are no plans to change anything besides adding a doc note to the Auth0 example. This is not an issue for other identity providers either.
Our team does not use issues for discussions => this will be locked.