MobileID

URL construction guide - Registration

44 views November 14, 2019 November 14, 2019 0

OIDC

Request

GET <SIGNICAT_AUTHORIZATION_ENDPOINT>?
response_type=code&; 
scope=openid+profile+mobileid&; 
client_id=<CUSTOMER_CLIENT_ID>&; 
redirect_uri=<CUSTOMER_CALLBACK_URL>&; 
state=<CUSTOMER_REG_METHOD_NAME:STATE_IDENTIFIER>&; 
acr_values=urn:signicat:oidc:method:<CUSTOMER_REG_METHOD_NAME>

Response

{
    "pairingCode": "<PAIRING_CODE>",
    "links": [
        {
            "rel": "status",
            "href": "<STATUS_URL>",
            "type": "GET"
        },
        {
            "rel": "complete",
            "href": "<COMPLETE_URL>",
            "type": "GET"
        },
        {
            "rel": "cancel",
            "href": "<CANCEL_URL>",
            "type": "GET"
        },
 		...
    ]
}

Notes

This is a regular authorization code flow. A request is sent to the authorization endpoint and upon successful registration, an authorization code will be sent to the customer’s backend (redirect to CUSTOMER_CALLBACK_URL).

SAML

Request

GET <SIGNICAT_BASE_URL>/std/method/<CUSTOMER_SERVICE>/? id=<CUSTOMER_REG_METHOD_NAME>::&target=<CUSTOMER_REDIRECT_URL>

Response

Signicat Page with information how to continue process

Notes

QR code scan or manually entering pairing code

Parameters

STATE_IDENTIFIER Random text used together with CUSTOMER_REG_METHOD_NAME to uniquely identify the
ongoing registration session in the customer’s backend.
The session state can be compared when callback data is received from Signicat.
PAIRING_CODE As described above. To be passed to the MobileID app.
STATUS_URL URL (towards Signicat’s server) that is used to get the status of the ongoing operation.
COMPLETE_URL URL (towards Signicat’s server) that is used to signal the completion of the transaction. This will need to be used when the customer’s app gets notification from the MobileID app that registration is complete.
CANCEL_URL URL (towards Signicat’s server) to cancel the ongoing operation.

Was this helpful?