| Informatie |
|---|
By default PKIsigning uses OpenIDconnect or OAuth2.0 SSO integrations. Only if this type of integration is not possible, a fallback can be implemented using information below. |
...
| Codeblok |
|---|
{
"Id":"internal unique id of integrating party indicating the user parmanently",
"Email":"emailaddress of the user",
"Mobilephone":"mobile number of user in international format",
"Surname":"Surname of user",
"Firstname":"First name of the user",
"Infix":"infix/prefix of lastname",
"OrganisationId":"id of the organisation as can be provided by application administrator"
} |
The content-type of the response should be text/json.
This backchannel call will be done immediately after the callback of step 3, so the used token doesn’t need to have a very long validity period.
...
.
Changing the redirecturl
Depending on the environment used, the user is directed to a specified PKIsigning IDP by the integrating partner: http://identity.pkisigning.io/connect/authorize?…
...
http://identity.pkisigning.io/connect/authorize?…&acr_values=idp:SSO_ID
Please note the colon-sign ( : ) between idp and the SSO_ID. This should preferrably encoded as %3A.
...