github
/
OpenID-Connect-Java-Spring-Server
mirror of https://github.com/mitreid-connect/OpenID-Connect-Java-Spring-Server
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Updated Features (markdown)

master
jricher 2013-04-25 13:39:17 -07:00
parent 7e9d646084
commit f861e126dd
1 changed files with 11 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
Features.md

@ -5,12 +5,12 @@ This page details our compliance level with the OpenID Connect specifications.
The following features are fully supported in our current implementation.
* Authorization code flow
* Implicit flow (pending an upstream change)
* Implicit flow
* UserInfo endpoint
* Manual client management through an administrator console
* HTTP Basic Auth for client authentication
* SWD discovery endpoint
* XRD discovery endpoint
* Webfinger discovery endpoint
* OpenID Configuration discovery endpoint
* JWK public key endpoint
* Standard scopes: openid, phone, address, email, profile
* Additional arbitrary scopes
@ -18,23 +18,18 @@ The following features are fully supported in our current implementation.
* RSA Signing
* HMAC Signing
* RSA Encryption
* Client filter with static single-server configuration
* Client filter with static multi-server configuration (using our Account Chooser)
* Dynamic registration endpoint
* Client filter
* Client filter dynamic registration
* Account chooser / third party login
* Request Objects (signed)
* Introspection Endpoint
* Revocation Endpoint
* Token chaining
## Currently unsupported / pending implementation / incomplete
The following features are not supported yet, but will be at some point. If we have a projected target for a given feature it will be listed here; if there is no projected target, that only means that we haven't set a target yet, not that it won't happen.
* Dynamic Client Registration (Fall FY12)
* Session management (FY13)
* X509 (Currently investigating how to publish our public keys as X509 certs)
* Request Object (Signed - in the works / Encrypted)
* Request File (Signed / Encrypted)
* Introspection endpoint (stubbed out, pending community standardization)
* Revocation endpoint (somewhat functional)
## Not targeted
The following features are things that we are not planning on supporting with our implementation, though we welcome pull requests and patches to incorporate these features:
* Dynamic client filter configuration (full server discovery)