...
client identifier
and aclient secret
Authentication URL
You might also need to provide a
redirect url
to your external identity provider. This is usuallyhttps://{authurl}/signin-oidc{callbackpathfromconfig}
Step 2 - Add/Configure External Identity provider
...
On the creation mask you have to provide the following data:
Property | Value | Description |
---|---|---|
| CoreOne Demo | The name of your external IdP |
| The IdP of the CoreOne Demo enviroment | A description for your external IdP |
| Customer.ExternalIdP.CoreOneDemo.Description | A translation key for the description |
| CoreOne Demo Login | A display name that is presented to users |
| Customer.ExternalIdP.CoreOneDemo.DisplayName | A translation key for the display name that is presented to users |
| - | An icon from the icon table if one has been defiend |
| Active | The state of the external IdP |
|
GenericOpenIdConnectOptions
| Depending on the type either select | |||||
|
|
|
|
|
|
|
|
|
| ||
|
oidc
| A unique scheme name | |
| https://demo-auth.itsense.ch | The URL where the user will be redirected to |
|
| Whether or not user shall be linked automatically. If disabled, the user will be presented with a confirmation screen. |
Step 3 - Define the attribute mapping
...
Example for Attribute Mappings:
Attribute | Identifies the user | Original Claim Type Name |
---|---|---|
|
| http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname |
|
| http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname |
|
| http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress |
Step 4 - Add the external provider to your Level of Authentication
...