Authentication | Users | Password |
---|---|---|
✔ | ✔ |
Note
OpenID Connect is a protocol based on REST, OAuth 2.0 and JOSE stacks. It is described here: http://openid.net/connect/.
LL::NG can act as an OpenID Connect Relying Party (RP) towards multiple OpenID Connect Providers (OP). It will get the user identity trough an ID Token, and grab user attributes trough UserInfo endpoint.
As an RP, LL::NG supports a lot of OpenID Connect features:
You can use this authentication module to link your LL::NG server to any OpenID Connect Provider. Here are some examples, witch their specific documentation:
France Connect | |
---|---|
![]() |
![]() |
Attention
OpenID-Connect specification is not finished for logout propagation. So logout initiated by relaying-party will be forward to OpenID-Connect provider but logout initiated by the provider (or another RP) will not be propagated. LLNG will implement this when spec will be published.
See OpenIDConnect service configuration chapter.
In General Parameters
> Authentication modules
, set:
Tip
As passwords will not be managed by LL::NG, you can disable menu password module.
Attention
Browser implementations of formAction directive are inconsistent (e.g. Firefox doesn’t block the redirects whereas Chrome does). Administrators may have to modify formAction value with wildcard likes *.
In Manager, go in :
General Parameters
> Advanced Parameters
> Security
>
Content Security Policy
> Form destination
Then in General Parameters
> Authentication modules
>
OpenID Connect parameters
, you can set:
To register LL::NG, you will need to give some information like application name or logo. One of mandatory information is the redirect URL (one or many).
To know this information, just take the portal URL and the Callback GET parameter, for example:
Attention
If you use the choice backend, you need to add the choice parameter in redirect URL or set SameSite cookie value to “Lax” or “None”. See SSO cookie parameters
After registration, the OP must give you a client ID and a client secret, that will be used to configure the OP in LL::NG.
In the Manager, select node OpenID Connect Providers
and click on
Add OpenID Connect Provider
. Give a technical name (no spaces, no
special characters), like “sample-op”;
You can then access to the configuration of this OP.
The OP should publish its metadata in a JSON file (see for example Google metadata). Copy the content of this file in the textarea. Portal discovery document can be found here: https://#portal#/.well-known/openid-configuration
If no metadata is available, you need to write them in the textarea. Mandatory fields are:
You can also define:
Example template:
{
"issuer": "https://auth.example.com/",
"authorization_endpoint": "https://auth.example.com/oauth2/authorize",
"token_endpoint": "https://auth.example.com/oauth2/token",
"userinfo_endpoint": "https://auth.example.com/oauth2/userinfo",
"end_session_endpoint":"https://auth.example.com/oauth2/logout"
}
JWKS is a JSON file containing public keys. LL::NG can grab them automatically if jwks_uri is defined in metadata. Else you can paste the content of the JSON file in the textarea.
Tip
If the OpenID Connect provider only uses symmetric encryption, JWKS data is not useful.
Define here the mapping between the LL::NG session content and the fields provided in UserInfo response. The fields are defined in OpenID Connect standard, and depends on the scope requested by LL::NG (see options in next chapter).
Claim name | Associated scope | Type | Example of corresponding LDAP attribute |
---|---|---|---|
sub | openid | string | uid |
name | profile | string | cn |
given_name | profile | string | givenName |
family_name | profile | string | sn |
middle_name | profile | string | |
nickname | profile | string | |
preferred_username | profile | string | displayName |
profile | profile | string | labeledURI |
picture | profile | string | |
website | profile | string | |
string | |||
email_verified | boolean | ||
gender | profile | string | |
birthdate | profile | string | |
zoneinfo | profile | string | |
locale | profile | string | preferredLanguage |
phone_number | phone | string | telephoneNumber |
phone_number_verified | phone | boolean | |
updated_at | profile | string | |
formatted | address | string | registeredAddress |
street_address | address | string | street |
locality | address | string | l |
region | address | string | st |
postal_code | address | string | postalCode |
country | address | string | co |
So you can define for example:
openid
scope is mandatory.client_secret_post
and client_secret_basic