-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
integration testing: OpendID Connect compliance tests #262
Comments
As we talked in dex-dev, here is the full report: |
Wow there's a lot of stuff in there. I'll take a look through them in a bit and try to come up with an issue list. Would you like to open a PR adding the compliance test scripts to this repo? Eventually (once we fix a sufficient number of them) I'd like to add them to the travis tests. |
I'm going to research about this. Some tests need user interaction and I don't know if it could work without an user. |
+1 |
Dex isn't yet [1,2] a certified OpenID Provider implementation. As of today, it's not on the list maintained by the OpenID Foundation. [3] [1] dexidp/dex#42 [2] dexidp/dex#262 [3] https://openid.net/certification/
Dex isn't yet [1,2] a certified OpenID Provider implementation. As of today, it's not on the list maintained by the OpenID Foundation. [3] [1] dexidp/dex#42 [2] dexidp/dex#262 [3] https://openid.net/certification/
Dex [isn't][1] [yet][2] a certified OpenID Provider implementation. As of today, it's not on the [list maintained by the OpenID Foundation][3]. [1]: dexidp/dex#42 [2]: dexidp/dex#262 [3]: https://openid.net/certification/ Signed-off-by: Etienne Dysli Metref <etienne.dysli@gmail.com>
Progress will be tracked here: https://github.com/orgs/dexidp/projects/3/views/1 |
This has been brought up as a precondition of #42 and #107 but I'm opening a new issue because it's worth addressing on its own.
Use outside compliance tests to evaluate dex's OpenID Connect implementation.
Relevant links:
The text was updated successfully, but these errors were encountered: