The IAS has the three environments but SPs SHOULD generally only integrate with the production and staging environments.

You should only need the issuer URI (sometimes called authority) for your integration, everything else can be configured automatically with Open ID Discovery. If you need to find other endpoints (eg authorization, token, userinfo and jwks) you can find them in the OpenID Configuration.


Issuer: https://innskra.island.is/

OpenID Configuration: https://innskra.island.is/.well-known/openid-configuration

Users: Real

The production environment is meant for SPs in production. It does not authenticate fake users.


Issuer: https://identity-server.staging01.devland.is/

OpenID Configuration: https://identity-server.staging01.devland.is/.well-known/openid-configuration

Users: Real and fake

The staging environment SHOULD be used when developing and testing an IAS integration.


Issuer: https://identity-server.dev01.devland.is/

OpenID Configuration: https://identity-server.dev01.devland.is/.well-known/openid-configuration

Users: Real and fake

The development environment is used internally at Island.is to develop and test new functionality.

SPs SHOULD NOT integrate with the development environment directly. Your development environment SHOULD integrate with the staging environment of IAS instead.

Fake users

In the development and staging environments you can authenticate into your client as fake users (Gervimenn). These can be useful to test different delegation scenarios.

You can request authentication details for fake users from island@island.is.

There is no two-factor authentication for fake users. This means anyone can authenticate and impersonate them. Depending on your App, you might need to host your dev/staging environments on internal networks, add secondary authentication or limit what users can do in these environments.

Last updated