# Environments

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.

## Production

> **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.

## Staging

> **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.

## Development

> **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](http://Island.is) to develop and test new functionality.

{% hint style="info" %}
SPs SHOULD NOT integrate with the development environment directly. Your development environment SHOULD integrate with the staging environment of IAS instead.
{% endhint %}

## 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>.

{% hint style="warning" %}
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.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devland.is/products/auth/environments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.