Connect2id server datasheet
1. OpenID certified provider
2. Identity and security profiles
Supported domain-specific OAuth 2.0 and OpenID Connect profiles:
- Financial API — Part 1: Read Only API Security Profile
- Financial API — Part 2: Read & Write API Security Profile
- HEART profile for OAuth 2.0
- HEART profile for OpenID Connect
- HEART profile for Fast Healthcare Interoperability Resources (FHIR) OAuth 2.0 scopes
Government / eID:
- International Government Assurance Profile (iGov) for OAuth 2.0
- International Government Assurance Profile (iGov) for OpenID Connect 1.0
3. Server endpoints
The Connect2id server implements all standard OAuth 2.0 / OpenID Connect endpoints for identity provision, xsingle sign-on (SSO) and issuing OAuth tokens. Powerful RESTful and native interfaces for enable integration of end-user, monitoring and administration UIs and tools.
Standard OAuth 2.0 / OpenID Connect endpoints
Server metadata — Publishes the URLs of the standard server endpoints, the authorisation and identity provision capabilities, the supported security algorithms.
Server JWK set — Publishes the server’s public JSON Web Key (JWK) set and certificate chain, required by client applications to validate ID tokens, self-contained access tokens and other issued objects.
Client registration — Registers client applications with the Connect2id server so they can request ID and / or access tokens. Supports the optional client read, update and delete operations.
Authorisation — Receives OAuth 2.0 authorisation requests and OpenID authentication requests from registered clients.
Token — Exchanges a valid OAuth 2.0 grant for an access, refresh and / or ID token.
Token introspection — Lets resource servers inspect issued access tokens. Can optionally return the introspection responses as a signed JWT.
Token revocation — Lets client applications revoke access and refresh tokens issued to them.
UserInfo — Releases consented claims (attributes) about the subject (end-user) to authorised clients.
Check session — Handles window.postMessage
polling for changes to the end-user authentication status with the OpenID Provider after the client has obtained an ID token.
- End session — Receives end-session notifications and logout requests from clients.
Integration & plugin interfaces
Authorisation session — For integrating a login page (UI), end-user authentication methods and policies for setting the scope and claims of issued tokens.
Logout session — For integrating an optional logout page (UI), for handling end-session requests and rendering front-channel logout iframes.
Direct authorisation — Facilitates direct issue of ID, access and refresh tokens. Can be used to implement custom OAuth 2.0 grants, issue tokens for special needs, integrate legacy systems.
Authorisation store — Enables query, update and revocation of issued OAuth 2.0 / OpenID Connect authorisations and the associated access and refresh tokens.
Subject session — Enables query, access and management of end-user sessions with the Connect2id server.
Monitoring — Publishes over 100 server usage and performance metrics, enables execution of health checks.
Claims source — Integrates OpenID Connect claims sources, such as LDAP directories, SQL databases and HR management systems.
Password grant handler — Enables plug-in of authorisation logic for handling OAuth 2.0 resource owner password credentials grants.
Client credentials grant handler — Enables plug-in of authorisation logic for handling client OAuth 2.0 credentials grants.
JWT bearer assertion grant handler — Enables plug-in of authorisation logic for handling client-issued and third-party issued (token service) JWT bearer grants.
SAML 2.0 bearer assertion grant handler — Enables plug-in of authorisation logic for handling client-issued and third-party issued (token service) SAML 2.0 bearer assertions grants.
Token issue event listeners — Enables plug-in of listeners for ID and access token issue events.
- Access token encoding and introspection — Enables plug-in of alternative access token codecs, shaping of token introspection responses.
4. Supported OAuth 2.0 / OpenID Connect response types
code — Used to obtain an ID, access and refresh token at the Token endpoint.
id_token — Used to obtain an ID token via the front-end (with browser redirection).
token — Used to obtain an access token via the front-end (with browser redirection).
token id_token — Used to obtain an ID token and access token via the front-end (with browser redirection).
code id_token — Used to obtain an ID token via the front-end (with browser redirection) in addition to an ID token and access token at the Token endpoint.
- code id_token token — Used to obtain an ID and access token via the front-end (with browser redirection) in addition to an ID token and access token at the Token endpoint.
5. Supported OAuth 2.0 response modes
The Connect2id server supports all standard OAuth 2.0 response modes:
query — Returns the response in the redirection URI query string.
fragment — Returns the response in the redirection URI fragment.
- form_post — Returns the response via a form post to the redirection URI.
6. Supported OAuth 2.0 grant types
The Connect2id server supports all core OAuth 2.0 grant types:
authorization_code — Used in the authorisation code flow.
implicit — Used in the implicit flow.
refresh_token — Used for long-lived authorisations.
password — Used for highly-trusted or privileged client applications, when the other safer grant types (e.g.
authorisation_code) are not available.
- client_credentials — Used by clients acting on their own behalf (the client is also the resource owner).
The following bearer assertions are also supported:
JWT Bearer — Using a signed JSON Web Token (JWT) as a grant.
- SAML 2.0 Bearer — Using a SAML 2.0 assertion as a grant.
Additional custom grants can be implemented via the endpoint for direct authorisation.
7. Supported OAuth client types
Confidential as well as public clients are supported:
Confidential clients — can maintain the confidentiality of their credentials, typically implemented on a secure server
- Public clients — cannot maintain the confidentiality of their credentials, typically clients on end-user devices
8. Proof key for code exchange (PKCE)
The Proof Key for Code Exchange (PKCE) protocol (RFC 7663) is supported to protect against authorisation code interception attacks on public OAuth clients.
The following code verifier transforms are supported:
- S256 — SHA-256 (mandatory to implement)
- plain — for legacy clients
9. Supported subject identifier types
The Connect2id server supports the following subject identifier types:
- public — Public subject identifier
- pairwise — Pairwise subject identifier, implemented by encrypting the public subject identifier with deterministic AES in SIV mode.
10. Authorisation and authentication request parameters
The Connect2id server supports all mandatory and optional OAuth 2.0 authorisation and OpenID authentication request parameters (see OpenID provider MTI:
OAuth 2.0: response_type, response_mode, client_id, scope, redirect_uri, state, code_challenge, code_challenge_method
- OpenID Connect: nonce, display, prompt, max_age, ui_locales, claims_locales, id_token_hint, login_hint, acr_values, claims, request, request_uri
Custom authorisation request parameters can also be implemented.
11. Supported client authentication methods
- client_secret_basic — Basic authentication with the client secret passed in the Authorization header.
- client_secret_post — Basic authentication with the client secret passed in the request body as form parameters.
- client_secret_jwt — JWT authentication using the client secret as shared HMAC key
- private_key_jwt — JWT authentication using public RSA or EC cryptography
- self_signed_tls_client_auth — Self-signed client X.509 certificate authentication
12. Supported ID token algorithms
The Connect2id server supports all standard JSON Web Algorithms for securing issued ID tokens by means of a digital signature, HMAC and optional additional encryption.
RS256, RS384, RS512, PS256, PS384, PS512, ES256, ES384, ES512 — The ID token is signed with a provider’s private RSA or EC key.
HS256, HS384, HS512 — The ID token is HMAC SHA protected with a key derived from the client secret.
RSA1_5, RSA-OAEP, RSA-OAEP-256, ECDH-ES, ECDH-ES+A128KW, ECDH-ES+A192KW, ECDH-ES+A256KW — The ID token is additionally encrypted with a client’s public RSA or EC key.
dir, A128KW, A192KW, A256KW, A128GCMKW, A192GCMKW, A256GCMKW — The ID token is additionally encrypted with an AES key derived from the client secret.
- none — The ID token is unsecured.
13. Supported UserInfo algorithms
The Connect2id server supports all standard JSON Web Algorithms for securing UserInfo JWT responses by means of a digital signature, HMAC and optional additional encryption.
RS256, RS384, RS512, PS256, PS384, PS512, ES256, ES384, ES512 — The
UserInfo JWT is signed with a provider’s private RSA or EC key.
HS256, HS384, HS512 — The UserInfo JWT is HMAC SHA protected with a key derived from the client secret.
RSA1_5, RSA-OAEP, RSA-OAEP-256, ECDH-ES, ECDH-ES+A128KW, ECDH-ES+A192KW, ECDH-ES+A256KW — The UserInfo JWT is additionally encrypted with a client’s public RSA or EC key.
- dir, A128KW, A192KW, A256KW, A128GCMKW, A192GCMKW, A256GCMKW — The UserInfo JWT is additionally encrypted with an AES key derived from the client secret.
14. Supported request object algorithms
The Connect2id server supports the following algorithms for securing request objects
RS256, RS384, RS512, PS256, PS384, PS512, ES256, ES384, ES512 — The
request object JWT is signed with a clients’s private RSA or EC key.
HS256, HS384, HS512 — The request object JWT is HMAC SHA protected with a key derived from the client secret.
- none — The request object JWT is unsecured.
15. Supported claim types
The Connect2id server supports all OpenID claim types:
normal — Claims directly asserted by the provider.
aggregated — Claims sourced from an external provider, made available as a signed JWT.
- distributed — Claims which can be obtained from the endpoint of an external provider using a supplied bearer access token.
16. OpenID Connect session management
Supported OpenID Connect session management and logout extensions:
OpenID Connect Session Management 1.0 (draft 28)
OpenID Connect Front-Channel Logout 1.0 (draft 02)
- OpenID Connect Back-Channel Logout 1.0 (draft 04)
Note: Connect2id server deployments with Redis as the primary in-memory store will not deliver back-channel logout notifications for expired sessions. This issue will be addressed in a future release
17. Offline access
The Connect2id server supports authorisations bound to a subject’s session as well as offline access by means of long-lived OAuth 2.0 refresh tokens.
18. Subject (end-user) authentication
Password-based authentication of end-users as well as stronger multi-factor methods are supported.
Upon successful login a client application can be informed of the employed authentication strength and methods, communicated through the standard acr and amr ID token claims.
19. Claims data sources
Sourcing of end-user claims from Microsoft Active Directory / LDAP is supported out of the box. A generic interface is available for connecting other claims sources, such as relational or NoSQL database, SCIM web services and HR systems.
20. Access tokens
Self-contained: The access token is encoded as a JSON Web Token (JWT). The JWT encapsulates all necessary authorisation details for relying resource servers to process requests from clients.
The JWT has an RSA signature, to be validated with the Connect2id server’s public key. All standard RSA signature algorithms are supported: RS256, RS384, RS512, PS256, PS384 and PS512. The JWT can optionally be encrypted with an AES key shared with the resource server(s) for confidentiality.
The following JWT claims (fields) are supported:
Claim Type Description iss string Issuer URL sub string Subject (end-user) ID act object Actor, in impersonation and delegation scenarios cid string Client ID aud string array Audience. Can be used to explicitly denote the protected resources for which the access token is intended. scp string array Token scope iat integer Issue time (seconds since Unix epoch). The token must not be accepted as valid before that time. exp integer Expiration time (seconds since Unix epoch). The token must not be accepted as valid after that time. jti string Secure random JWT identifier. clm string array Names of any consented OpenID claims cll string array Preferred claims locales uip object Preset OpenID claims for release at the UserInfo endpoint cnf.x5t#S256 object Confirmation of client X.509 certificate dat object Optional data
An SPI is provided for plugging alternative JWT claim encodings.
Self-contained token can also be inspected by a call to the Connect2id token introspection endpoint.
Identifier-based: The access token is represented by a secure random 128 bit identifier, protected with an SHA-256 HMAC truncated to 128 bits. The authorisation details are looked up by a call to the Connect2id token introspection endpoint.
An SPI is provided for plugging alternative identifier generators.
Identifier-based tokens are intended for clients which cannot validate RSA signatures, or for applications which security requires revocation with immediate effect.
20.1 Client X.509 certificate bound access tokens
When mutual TLS is used at the token endpoint, the Connect2id server binds the issued access token to the client’s X.509 certificate. Resource servers can validate the binding by inspecting the x5t#S256 access token claim which represents the SHA-256 thumbprint of the client certificate.
21. Refresh tokens
The Connect2id server issues refresh tokens based on secure 128 bit random identifiers.
Refresh token lifetime (default setting is no expiration).
- Refresh token update on each use and authorisation update (default setting is no update).
Impersonation use cases are supported:
Issue of impersonated ID tokens to enable privileged users to log into a client under a different identity.
- Issue of impersonated access and refresh tokens to enable privileged users to access protected resources under a different identity.
The Connect2id server provides a web API for querying, updating and revoking impersonated tokens and authorisations.
23. Metrics and monitoring
24. High-availability and scaling
The Connect2id server can be run in two modes:
Standalone — The Connect2id server runs in a single JVM.
- Cluster — Two or more Connect2id server nodes are
clustered for high-availability and
load-balancing. Server nodes can be added or removed dynamically. Supported
- Replication — in-memory and cached data, such as sessions, is replicated between the Connect2id server nodes;
- Stateless — in-memory and cached data is stored in a external Redis database; for very large user bases and quick, dynamic up / down scaling.
- Java 8+ JVM
- Servlet 3.0+ compatible container: Apache Tomcat 7+
26. Backend databases
The Connect2id server supports the following backend databases:
For persisting durable data, such as client registrations and long-lived authorisations:
- Relational database:
- MySQL 5.7.8+ (incl. compatible MariaDB editions and AWS AuroraDB DBaaS, 8.x not officially supported yet)
- PostgreSQL 9.5+ (incl. compatible MariaDB editions and AWS AuroraDB DBaaS)
- H2 1.4+ (for testing and development only)
- LDAP v3 directory: OpenLDAP 2.4+, OpenDJ 2.6+
- AWS DynamoDB
For in-memory storage and caching outside Infinispan:
- Redis (including AWS ElastiCache with Redis backend)
27. Hardware Security Module (HSM) support
For signing issued ID tokens and self-contained (JWT) access tokens.
RSA and EC with P-256, P-384, and P-521 curves.
- Automatic key roll-over according to the validity window of the key’s
Questions or comments?
Get in touch with Connect2id support.