OIDC OP

Overview

The OIDC OP plugin is the successor to the original GEANT-funded add-on to Shibboleth and is now available as an offically-supported plugin for IdP V4.1 and above. It provides conformant OIDC OP functionality alongside the SAML and CAS support previously native to the IdP software.

Starting with V3.1, the plugin also includes support for some OAuth 2 features, acting as a more generalized Authorization Service in the OAuth framework.

Please review the OPReleaseNotes when installing or upgrading a new version.

Implemented specifications

• OpenID Connect

  • Core: https://openid.net/specs/openid-connect-core-1_0.html

  • Discovery: https://openid.net/specs/openid-connect-discovery-1_0.html (Provider Metadata)

  • Dynamic Client Registration: https://openid.net/specs/openid-connect-registration-1_0.html (Client Metadata and Registration Endpoint)

  • RP-Initiated Logout^4.1: https://openid.net/specs/openid-connect-rpinitiated-1_0-final.html

  • Front-Channel Logout^4.1: Final: OpenID Connect Front-Channel Logout 1.0

  • Back-Channel Logout^4.1: Final: OpenID Connect Back-Channel Logout 1.0 incorporating errata set 1

• OAuth2

  • RFC6750: RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage

  • RFC7009: RFC 7009: OAuth 2.0 Token Revocation

  • RFC7636: RFC 7636: Proof Key for Code Exchange by OAuth Public Clients

  • RFC7662: RFC 7662: OAuth 2.0 Token Introspection

  • RFC8707^3.2: RFC 8707: Resource Indicators for OAuth 2.0

  • RFC9068^3.2: RFC 9068: JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens

  • RFC9101^4.2: RFC 9101: The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)

  • RFC9126^4.2: RFC 9126: OAuth 2.0 Pushed Authorization Requests

  • RFC9207^3.2: https://www.rfc-editor.org/rfc/rfc9207.html

  • RFC9449^4.2: https://www.rfc-editor.org/rfc/rfc9449.html

Plugin Installation

Please review the OPReleaseNotes when installing or updating this plugin.

Enabling the Module

For a detailed guide on configuring modules, see the ModuleConfiguration topic. Once the plugin has been installed, its module should be enabled automatically for you:

Check Module Is Enabled

However, if you need to enable it you can using the module command:

Enable the module

When enabled, a number of new configuration files will be created for further customization.

Systems upgraded to V4.1 are also likely to require adding the idp.searchForProperties=true property to their idp.properties file, or else an explicit reference would have to be added to the new property file added by the module. It's best to clean up the property loading situation prior to using plugins that add their own.

Initial Setup

Because this plugin is considerably more extensive than most, there are more touchpoints to the rest of the IdP configuration and a larger-than-usual set of initial setup steps needed before it can be used. The IdP may not even startup properly until some of them are completed.

First Steps

Add an import statement to conf/credentials.xml:

Adjust or add the idp.searchForProperties setting in idp.properties and set it to true to auto-locate and load the new properties file. This will extend to other new features in the future, so makes adding and removing new functionality simpler.

If you want to leverage the new default claim mapping rules, you can add an import to conf/attributes/default-rules.xml:

The impact of this is to reduce the need for <AttributeDefinition> and <AttributeEncoder> elements in your Attribute Resolver configuration when adhering to "default" expectations for the names of attributes and how they map into OIDC claims. We encourage this as it makes things simpler and more consistent but it isn't mandatory.

The additional files created in conf/examples (oidc-attribute-resolver.xml and oidc-attribute-filter.xml) are intended as a source of examples to copy into your own files. The most critical definitions needed are the rules for creating and releasing the "sub" claim, as that is a required OIDC feature (see OIDC OP#ClaimSetup). If you want to use the example files directly (unlikely), you can copy them elsewhere and make use of them as you see fit.

Key Generation

The OP plugin supports keys in the JWK format as well as the more typical PEM format. There are some advantages to using the JWK format in optimizing which keys are tried in certain cases. There is no particular advantage to reusing any existing keys your IdP may be using, but you can if you prefer to do so.

The default configuration expects to have two RSA keys (one for signing and one for decryption), and one EC key. They are expected to be in locations defined via the following properties (with the shipping defaults shown):

• idp.signing.oidc.rs.key - %{idp.home}/credentials/idp-signing-rs.jwk

• idp.signing.oidc.es.key -%{idp.home}/credentials/idp-signing-es.jwk

• idp.signing.oidc.rsa.enc.key - %{idp.home}/credentials/idp-encryption-rsa.jwk

Keys may be generated using the provided wrappers, in bin/jwtgen.sh and bin/jwtgen.bat:

Key Generation Example

OIDC Issuer and Discovery

The OIDC "issuer" value needs to be determined, and the OpenID discovery document needs to be made accessible.

The issuer value is set in conf/oidc.properties and must be a URL using the "https" scheme that contains host, and optionally, port number and path components and no query or fragment components. It generally must resolve to the root of the deployment in question. As a result, while it may be the same as one's SAML entityID, it often cannot be, as SAML does not conflate identity and location in this fashion.

conf/oidc.properties

A common way for clients to configure themselves against an OP is to read the openid-configuration resource as defined in https://openid.net/specs/openid-connect-discovery-1_0.html.

A template for this file is created in static/openid-configuration.json. You will need to update it to match your configuration. At minimum this means replacing "{{ service_name }}" with the host portion of your issuer value.

In order for clients to locate the file, you will either have to:

• Configure your Java container or other web server "front-end" to publish it at this exact location (obviously the prefix depends on your issuer value):

• Or (more typically), configure that location to route into your IdP at /idp/profile/oidc/configuration to generate the document more dynamically.

The OPDiscovery topic describes this further.

Enabling Profiles

Activating support for OIDC, as with other protocols supported, requires adjusting the RelyingPartyConfiguration in conf/relying-party.xml.

One of the profiles (the one that advertises keys) needs to be openly accessible:

conf/relying-party.xml

The rest are functional profiles that may be enabled more selectively but would normally be enabled by default:

conf/relying-party.xml

Obviously this relies on a lot of defaulted behavior, but the full documentation includes more detailed information about how to adjust profile settings.

Claim Setup

Attributes in OIDC are termed claims, but the IdP treats them just as in other protocols, with the usual resolution and filtering approaches. You will need to reference that documentation early on in the testing process and you will also want to take some care regarding the "sub" claim.

Example RP

For initial testing, it's helpful to start simple and add an example RP by hand. There are several different ways of managing RP registration data, but for a quick test, the simplest is to add some static JSON to the system to define a test system.

There are some commented options in conf/oidc-clientinfo-resolvers.xml that can be uncommented to supply an example JSON file to load:

conf/oidc-clientinfo-resolvers.xml

This in turn allows you to statically define a JSON array of client registrations in a file:

metadata/oidc-client.json

You will of course need to adjust the JSON to match the client you are testing, for which the documentation should help.

Full Configuration

Please refer to the topics below for more detailed information on different aspects of the extension.

• Client Registration (Metadata and Dynamic)

• Client Resolution

• User Authentication

• Client Authentication

• Attribute/Claims Resolution

  • The "sub" Claim

• Attribute Filtering

• Security Configuration

• Profile Configuration

• OP Discovery

Use Cases

• Client Credentials Grant

• Authorization Code Affinity