...
eSignering.no offers a REST API for administration of both signing and authentication. Authentication is the simplest one, so basically the application can order a authentication session and verify the result
after authentication is performed.
Start a session
...
POST |
|---|
/rest/v1/ |
...
autentisering |
Query parameters: retur – a call-back url to redirect after authentication (Mandatory) |
...
...
Optional parameters: |
...
err – a separate url for error |
...
handling fnr – to specify the SSN to expected (will not be asked for). This will guarantee that the authenticated person has such a SSN otherwise the result will be false. |
...
height – The height of the BankID client (Default: 300) |
...
width – The width of the BankID client (Default: 400) |
...
confirm – Should the BankID dialogue ask the user to confirm? (Default: true) |
...
understand – Should the BankID dialogue ask the user to click |
...
“I understand” (Default: true) |
...
...
Headers: |
...
...
Basic authentication header with your username and password or Bearer token header with token fetched from Ambitas |
...
authentication REST service |
Description Creates a authentication session for your user. |
...
Response: The details on the authentication as |
...
JSON |
...
Example: |
...
|
...
|
...
...
|
...
|
...
|
...
...
The retururl is the gui client (to be embedded or redirected to) |
...
...
The sid is the unique reference to this session, to be used to get the result of the authentication session. |
...
Embedd the BankID client into your pages
...