OpenID Connect service configuration¶
Go in Manager and click on
OpenID Connect Service node.
Set the issuer identifier, which should be the portal URL. For example: http://auth.example.com
Set a blank value to use Portal URL.
Name of different OpenID Connect endpoints. You can keep the default values unless you have a specific need to change them.
- User Info
- End of session
- Check Session
- Front-Channel URI
- Back-Channel URI
These endpoints are published in JSON metadata.
You can associate here an authentication context to an authentication level.
- Keys: Define public/private key pair for asymmetric signature. A JWKS
kid(Key ID) is automatically derived when new keys are generated.
- Authorization Code flow: Set to 1 to allow Authorization Code flow
- Implicit flow: Set to 1 to allow Implicit flow
- Hybrid flow: Set to 1 to allow Hybrid flow
- Only allow declared scopes: By default, LL::NG will grant all requested scopes. When this option is enabled, LL::NG will only grant:
- Authorization Codes: Expiration time of authorization code. Default value is one minute.
- ID Tokens: Expiration time of ID Tokens. Default value is one hour.
- Access Tokens: Expiration time of Access Tokens. Default value is one hour.
- Offline sessions: This option sets lifetime of Refresh Tokens
offline_accessscope. Default value is one month.
Best pratice is to use a separate sessions storage for OpenID Connect sessions, else they will be stored in main sessions storage.
- Activation: Set to 1 to allow clients to register themselves
If Dynamic Registration is enabled, you can configure the following
options to define attributes and extra claims released when a new relying
party is registered through
- Exported vars
- Extra claims
Dynamic Registration can be a security risk because a new configuration will be created in the backend for each registration request. You can restrict this by protecting the WebServer registration endpoint with an authentication module, and give credentials to clients.
Keys rotation script¶
OpenID Connect specifications allow to rotate keys to improve security. LL::NG provides a script to do this, that should be used in a cronjob.
The script is
/usr/share/lemonldap-ng/bin/rotateOidcKeys. It can be
run for example each week:
5 5 * * 6 www-data /usr/share/lemonldap-ng/bin/rotateOidcKeys
Set the correct WebServer user, else generated configuration will not be readable by LL::NG.
LL::NG implements the OpenID Connect Change Notification specification
changed state will be sent if the user is disconnected from LL::NG
portal (or has removed its SSO cookie). Else the
will be returned.
This feature requires that the LL::NG cookie is exposed to
httpOnly option must be set to