OpenID compliance test uses a draft spec #10972
-
Describe the bugThe OpenID validation function [1] is checking whether Since providers might not be configured to specify that endpoint while still being compliant, we should not base the validation on it. [1] [2] https://openid.net/specs/openid-connect-session-1_0.html [3] https://openid.net/specs/openid-connect-session-1_0-17.html Related PR #10012 ### Reproduction steps
Expected behaviorThe OpenID compliance should still be validated even without logout endpoint. Additional contextIf anyone is facing a similar issue while using Auth0, you can still enable that endpoint. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
@elythh our OAuth 2 and OpenID Connect implementations target the needs of paying users. There are five example configurations that use very popular identity provider tools, including Auth0. Also, if you want the core team to spend any time on your proposal, it must be a detailed explanation of the alternatives and their downsides, not a three sentence long problem definition. "Configure RabbitMQ with Auth0 as provider" is not a reproduction step, there are many many variables involved in any practical OAuth 2-enabled setup. Thanks for providing [1], it can be added to the docs for Auth0. |
Beta Was this translation helpful? Give feedback.
-
Oh sorry about the duplicate issue and the mistake, I didn't get notified about this discussion. |
Beta Was this translation helpful? Give feedback.
-
@elythh This docker image pivotalrabbitmq/rabbitmq:make-end-session-endpoint-optional (it will be released as 3.13.2) makes the claim |
Beta Was this translation helpful? Give feedback.
-
FTR, we have encountered a similar complaint from a paying user and the issue to watch is #11067 (and as can be seen above, we already have a spike by @MarcialRosales). |
Beta Was this translation helpful? Give feedback.
@elythh our OAuth 2 and OpenID Connect implementations target the needs of paying users. There are five example configurations that use very popular identity provider tools, including Auth0.
Also, if you want the core team to spend any time on your proposal, it must be a detailed explanation of the alternatives and their downsides, not a three sentence long problem definition. "Configure RabbitMQ with Auth0 as provider" is not a reproduction step, there are many many variables involved in any practical OAuth 2-enabled setup.
Thanks for providing [1], it can be added to the docs for Auth0.