> For the complete documentation index, see [llms.txt](https://docs.devland.is/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devland.is/products/auth/environments.md).
# Environments
The IAS has the three environments but SPs SHOULD generally only integrate with the production and development 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:**
>
> **OpenID Configuration:**
>
> **Users:** Real
The production environment is meant for SPs in production. It does not authenticate fake users.
## Staging
> **Issuer:**
>
> **OpenID Configuration:**
>
> **Users:** Real and fake
{% hint style="warning" %}
The staging environment has been **deprecated**. SPs SHOULD integrate with the development environment instead when developing and testing an IAS integration.
{% endhint %}
## Development
> **Issuer:**
>
> **OpenID Configuration:**
>
> **Users:** Real and fake
The development environment SHOULD be used when developing and testing an IAS integration.
## 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 .
{% 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 %}