Versions Compared

Old Version 14

changes.mady.by.user Mustafa Korkmaz

Saved on

compared with

New Version 15

changes.mady.by.user Mustafa Korkmaz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Creates a new authentication. (Step 2)

If succeeds, returns authenticationId as a GUID in the location header. (Step 3)

Payload parameter name

Description

partnerId

Desired NEXT PartnerId

method

Authentication method to use:

nbid, nbid-mobil Norwegian BankID / Mobile

sbid, sbid-mobil Swedish BankID / Mobile

identity

Identity (personal number / social security number) to verify against

callbackUrl

Your url that user will be redirected back to as shown in step 8.. (Step 8)

AuthenticationId value will be appended as a query string parameter with id name when Identity API calls you back.

customProperties

An optional <string, string> Dictionary that your custom properties are stored on the authentication.

...

End user should be opening this page upon a new authentication is created and authenticationId is claimed. (Step 4)

Info

Upon opening this page, end user will be redirected to the corresponding service provider’s authentication page. (Step 5)

Route parameter name

Description

authenticationId

Location header value claimed after succesful [POST] /api/authentications request

partnerId

Desired NEXT PartnerId

...

It could be called anytime once an authentication is created. The best case for you business to call this endpoint would be the place where you check whether the user authentication is complete or not. (Step 9)

Route parameter name

Description

authenticationId

Location header value claimed after succesful [POST] /api/authentications request

partnerId

Desired NEXT PartnerId

...