IAS has an admin interface which can be used to define new Clients(applications) and Scopes(permissions). An organisation can request access to this admin interface by contacting and then grant developers access on behalf of the organisation.

Configuring IAS organisation

Organisations in IAS serve as containers for clients and scopes. They have these fields:

  • National ID: The national ID of the organisation.

  • Domain: The primary domain for the organisation, used as a prefix in client, resource and scope names; e.g.

  • Contact Email: Email which Digital Iceland can use for service notifications and issues.

Defining clients

When defining clients, you need to provide the following:

  • Client Type: Web Client, Native Client (for mobile apps) or Machine Client (client credentials).

  • Client ID: Should follow naming convention @{domain}/{clientName}

  • Client Secret: Required for web and machine clients.

  • Display Name: What the user sees when logging into your application.

  • Supported Delegations: What kind of delegations to support (Legal Guardian, Personal Representative, Procuring Holders, Custom).

  • Prompt Delegations: Determines if users will be prompted to choose a delegation when signing into your app.

  • Allow Offline Access: Should the client be able to get refresh tokens.

  • Refresh Token Expiration: Inactive vs Absolute expiration of refresh tokens in seconds.

  • Redirect Uri: Which callback URIs should be allowed when logging in with this client. In the staging environment you can use wildcard tokens (*) to support feature deployed subdomains, e.g. https://*

  • Post Logout Uri: Which URIs should be allowed when logging out of this client.

  • Identity Providers: Specifies which Identity Providers to be used when authenticating to this client.

  • Grant Types: What kind of authentication flow the client will use. Authorization Code for web and native clients. Client Credentials for machine clients and optionally allow for token exchange.

  • Scopes: Which scopes should the client be able to request.

Supported identity providers

IAS currently supports three identity providers, all of which provide a high level of assurance with digital certificates issued to hardware devices in-person.

Clients can configure which identity providers they want to support:

SIM Card

This uses electronic ID saved on SIM cards in mobile phones.

Identity Card

The Identity Cards look like credit cards and have electronic IDs saved on them. They require a dedicated card reader to use.

Mobile App

The newest Identity Provider is a mobile app called Auðkennisappið where the electronic ID is saved in secure device storage.

Defining scopes

If you want to use IAS access tokens to authorise requests to your APIs you must define one or more scopes for the API’s endpoints.

Scope configuration:

  • Name: Should follow naming convention @{domain}/{scopeName}

  • Display Name: Shown on consent screen.

  • Description: Shown on consent screen.

  • Supported delegations: What kind of delegations can use this scope (Legal Guardian, Personal Representative, Procuring Holders, Custom).

  • Personal Representative Permissions: Which personal representative permissions, if any, gives access to this scope.

  • Claims: Which user claims do the API endpoints need in the access token (e.g. nationalId).


Let's say your organisation's domain is, with a web app on which uses IAS to authenticate normal users and needs an access token to talk to a "Document API" hosted on

You can create the following IAS resources:

Webapp client

  • Client Type: Web Client

  • Client ID:

  • Client Secret: ...

  • Display Name: My Org Webapp

  • Supported Delegations: None

  • Prompt Delegations: No

  • Allow Offline Access: Yes

  • Refresh Token Expiration: 30m inactive, 24h absolute

  • Redirect Uri:

  • Post Logout Uri:

  • Identity Providers: All

  • Grant Types: Authorization Code

  • Scopes: and

Document API's read documents scope

  • Name:

  • Display Name: Read documents

  • Description: Read access to the user's documents.

  • Supported delegations: None

  • Claims: nationalId

Document API's write documents scope

  • Name:

  • Display Name: Write documents

  • Description: Read/Write access to the user's documents.

  • Supported delegations: None

  • Claims: nationalId

Even though the name field of clients and scopes have the same naming convention, they won't conflict with each other and there's no associations based on the name.

Example authentication

  1. User goes to which has the client.

  2. The user clicks a login button. The client sends them to the IAS authorize endpoint: with these query parameters:


    • redirect_uri=

    • response_type=code

    • scope=openid profile offline_access

    • state={SOME_STATE}

    • code_challenge={CODE_CHALLENGE}

    • code_challenge_method=S256

    • response_mode=query

  3. The user authenticates and IAS sends the user to the client callback URL: with these query parameters:


    • scope=openid profile offline_access

    • state=SOME_STATE

  4. The client performs a POST request to the IAS token endpoint: with the following payload encoded as content-type: application/x-www-form-urlencoded:



    • redirect_uri=

    • code_verifier={CODE_VERIFIER}

    • grant_type=authorization_code

  5. The client receives the ID token, access token and refresh token in the response:

      "id_token": "{idToken}",
      "access_token": "{accessToken}",
      "refresh_token": "{refreshToken}",
      "expires_in": 300,
      "token_type": "Bearer",
      "scope": "openid profile offline_access"
  6. The client can decode the ID token or call the userinfo endpoint: with the access token to get authentication claims:

      "sub": "{subject}",
      "nationalId": "{userNationalId}",
      "subjectType": "person",
      "name": "{userFullName}",
      // Additional when delegation
      "delegationType": [
      "actor": {
        "nationalId": "{userNationalId}",
        "name": "{userFullName}"
  7. The client can use the access token to call the documents API: When decoded and validated the access token also contains claims about the authenticated user:

      "nbf": { notValidBeforeTime },
      "exp": { expiryTime },
      "iat": { issuedAtTime },
      "auth_time": { authenticationTime },
      "iss": "",
      "client_id": "",
      "sub": "{subject}",
      "idp": "{identityProvider}",
      "nationalId": "{userNationalId}",
      "jti": "{tokenId}",
      "sid": "{sessionId}",
      "scope": "openid profile offline_access",
      "amr": [{authenticationMethod}],
      "acr": "eidas-loa-high"

Example sign-out

  1. User is using the site which has the client.

  2. The user clicks a logout button. The client redirects them to the IAS /endsession endpoint: with these query parameters:

    See additional support query parameters in the OpenID Connect RP Initiated Logout Specification.

  3. If the post_logout_redirect_uri is valid, IAS redirects the user back to the client using that URI.

Last updated