# OpenID Provider Configuration

Singpass' authorization server exposes an endpoint from which you can retrieve metadata about how Singpass is configured as an OpenID Provider:

<table><thead><tr><th width="199">Environment</th><th>Discovery Endpoint</th></tr></thead><tbody><tr><td>Staging</td><td><a href="https://stg-id.singpass.gov.sg/fapi/.well-known/openid-configuration">https://stg-id.singpass.gov.sg/fapi/.well-known/openid-configuration</a></td></tr><tr><td>Production</td><td><a href="https://id.singpass.gov.sg/fapi/.well-known/openid-configuration">https://id.singpass.gov.sg/fapi/.well-known/openid-configuration</a></td></tr></tbody></table>

The metadata hosted at this endpoint is crucial for your integration. It tells you things like:

* The various endpoints and URIs that you will need, and
* Supported scopes, response types, and encryption/signing algorithms

Because [OpenID Connect Discovery](https://openid.net/specs/openid-connect-discovery-1_0.html) is part of the OIDC spec, if you are using an OpenID-certified relying party library, the library may automatically retrieve metadata from our discovery endpoint for you. In such cases, you may not be aware of this detail.

Please be aware, however, that Singpass' OpenID configuration is not static, and you should regularly fetch from our discovery endpoint to ensure freshness. At the same time, you should also avoid fetching from this endpoint too frequently, e.g. for every authentication request. Instead, consider caching responses for at least an hour.


---

# 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.developer.singpass.gov.sg/docs/technical-specifications/technical-concepts/openid-connect-discovery.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.
