...
This step covers registering a new Application in the IDConnect back-end and configureing configuring platform settings such as the conenction connection to Trust&Sign for the IDConnect middleware
...
Parameter | Value | Field Mapping Configuration | Comment |
---|
|
| Field Property Path | Mode | Data Field |
|
---|
Provider Name | e.g. "Netheos Trust&Sign" |
|
|
| Will be shown in eSAW to select the authentication/identification method, and will be shown to the signer in authentication method selection. |
Client Id | (use the client ID created in step 2. It should have been provided by Namirial sales or presales team) |
|
|
| TEST ClientID for Christoph's Test Org: 09c11f68-2212-4a91-8070-105ba414fc71 |
Client Secret | (use the client secret created in step 2. It should have been provided by Namirial sales or presales team) |
|
|
| TEST Client Sectet for Christoph: Slack message LR to CB, Tue 26/04/2022 in combination with above's Client ID |
Scope | openid profile email trustsign |
|
|
|
|
Authorization URI | https://esaw-ts-api-demo.namirial.com/identityserver/connect/authorize |
|
|
|
|
Token URI | https://esaw-ts-api-demo.namirial.com/identityserver/connect/token |
|
|
|
|
Logout URI |
|
|
|
|
|
JSON Web Token (JWT) Configuration |
|
|
|
|
|
| JWKS URI | https://esaw-ts-api-demo.namirial.com/identityserver/.well-known/openid-configuration/jwks |
|
|
|
|
| Issuer | https://esaw-ts-api-demo.namirial.com/identityserver |
|
|
|
|
| Add 'nonce' parameter | Off |
|
|
|
|
| Validate audience | Off |
|
|
|
|
| Validate issuer | On |
|
|
|
|
| Validate lifetime | On |
|
|
|
|
| Field Mapping |
| given_name | Validate | Recipient First Name | Note that this is a validation rule to ensure that the signer is the one which the sender defined. When providing an UPDATE rule for the given errror, IDConnect currently returns "Invalid parameter 'firstName' format (Invalid value)":
|
| Field Mapping |
| family_name | Validate | Recipient Last Name | Note that this is a validation rule to ensure that the signer is the one which the sender defined |
| Field Mapping |
| identification_type | Update | Disposable Certificate Identification Type |
|
| Field Mapping |
| document_type | Update | Disposable Certificate Document Type |
|
| Field Mapping |
| identification_number | Update | Disposable Certificate Identification Number |
|
| Field mapping | (leave out this one for now!!) |
|
| Disposable Certificate Phone Number | 20220530: not available in demo process! If left out, it has to be set by the sender in eSAW. |
| Field Mapping |
| issuing_country | Update | Disposable Certificate Document Issuing Country |
|
| Field Mapping | (leave out this one for now!!) |
| Update | Disposable Certificate Issued By | 20220530: not available in demo process! If left out, it has to be set by the sender in eSAW. Depending on TSP rules, it might be allowed to use a static value which references to Trust&Sign. |
| Field Mapping |
| document_number | Update | Disposable Certificate Document Number |
|
| Field Mapping |
| identification_country | Update | Disposable Certificate Identification Country |
|
| Field Mapping | (leave out this one for now!!) |
| Update | Disposable Certificate Document issued On | 20220530: not available in demo process! Depending on TSP rules, it might be allowed to use some artificial value if Trust&Sign process that doesn't return this date is approved. |
| Field Mapping |
| expiry_date | Update | Disposable Certificate Document ExpirationExpiry Date |
|
Attention:
- Trust&Sign (in this configuration) does NOT offer a phone number. Therefore, the phone number must not be set as UPDATE rule in e.g. another identification configuration which is used as backup option.
- Trust&Sign (in this configuration) does NOT offer a document issuing date.
- Trust&Sign (in this configuration) does NOT offer an issuing authority name ("issued by").
...