Toolkit for developing Connect2id Server connectors and extensions
- Java Service Provider Interface (SPI) for sourcing OpenID Connect claims
about a subject (end-user), such as email, name, phone number and address.
Used by the Connect2id Server in its OpenID Connect Provider (OP) role to
aggregate claims from one or more sources (LDAP, RDMBS, etc).
- SPI for handling resource owner password credential grants (see RFC 6749,
section 4.3). Used by the Connect2id Server to delegate validation of the
submitted username / password and authorisation for the requested token.
- SPI for handling client credential grants (see RFC 6749, section 4.4). Used
by the Connect2id Server to delegate authorisation for the requested token.
- SPI for handling client-issued (self-issued) JWT bearer assertion grants
(see RFC 7523, section 2.1). Used by the Connect2id server to delegate
authorisation for the requested token.
- SPI for handling client-issued (self-issued) SAML 2.0 bearer assertion
grants (see RFC 7522, section 2.1). Used by the Connect2id server to
delegate authorisation for the requested token.
- SPI for handling third-party issued SAML 2.0 bearer assertion grants (see
RFC 7522, section 2.1). Used by the Connect2id server to delegate validation
of the SAML 2.0 assertion and authorisation for the requested token.
Download
Official releases of the Connect2id Server toolkit are pushed to Maven Central
under
GroupId: com.nimbusds
ArtifactId: c2id-server-sdk
These include the library’s source code, compiled JAR and JavaDocs.
To add the SDK to your Maven project use the following template:
<dependency>
<groupId>com.nimbusds</groupId>
<artifactId>c2id-server-sdk</artifactId>
<version>[version]</version>
</dependency>
where [version] should match the expected by the particular
Connect2id Server version you're running.
Questions or comments?
Email [email protected]