...
tia® Connect to tia®Core CMIS
There are two options
Authentication via client_secret
Authentication via certificate
For client_secret authentication, only a client ID and a client secret need to be configured.
For certificate authentication, a keystore containing the key pair must be provided. A certificate must be generated from this and imported into the app registration.
The client-authentication-method tls_client_auth or self_signed_tls_client_auth needs to get configured. The name of the configured SSL bundle needs to get configured into the tia.security.oidc.sslBundleName property.
How exactly this is configured is described as follows
Parent | Parameter | Description | Required |
|---|---|---|---|
|
| Issuer URI of the authorization server | yes |
|
| The name of the attribute in the token that references the Name or Identifier of the end-user | no |
|
| Name of the configured provider | yes |
|
| The client identifier | yes |
|
| The client secret | yes |
|
| A credential representing the resource owner's authorization used by the client to obtain an access token | yes |
|
| The scope(s) requested by the client during the authorization request | yes |
|
| The authentication method used when authenticating the client with the authorization server. Only needs to get overwritten with | no |
|
| Key alias | no |
|
| Key password | no |
|
| Path to the keystore | no |
|
| Keystore password | no |
|
| Type of the keystore, e.g. | no |
...