> For the complete documentation index, see [llms.txt](https://docs.corppass.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corppass.gov.sg/technical-specifications/corppass-authorization-api-fapi-2.0/integration-guide/1.-pushed-authorization-request-par-endpoint/authentication-context-parameters.md).

# Authentication Context Parameters

New parameters have been introduced in the authorization flow to help contextualise each authorization request via [Pushed Authorization Request](/technical-specifications/corppass-authorization-api-fapi-2.0/integration-guide/1.-pushed-authorization-request-par-endpoint.md).

These parameters are not part of the standard OpenID Connect (OIDC) specification and are specific to the [Corppass Login](/products/corppass-login.md).

<table data-header-hidden><thead><tr><th width="296.75" valign="top">Field</th><th width="110.55859375" valign="top">Required</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top"><code>authentication_context_type</code></td><td valign="top">Yes</td><td valign="top"><p>A value from a predefined list describing the type of transaction for which the user is authenticating. This context is used by Corppass for risk assessment and anti-fraud monitoring.</p><p></p><p><strong>Validation:</strong></p><ul><li>Must be one of the supported types configured for your specific client application.</li><li>Values not allow-listed for your client ID will be rejected.</li><li>This parameter is applicable only for Corppass Login application. If provided for Myinfo Business application, the request will be rejected.</li></ul><p>The list of supported values is provided below.</p></td></tr><tr><td valign="top"><code>authentication_context_message</code></td><td valign="top">No</td><td valign="top"><p>Optional. A string providing context on the purpose of the authentication request.​</p><p></p><p><strong>Validation:</strong></p><ul><li>Must contain only alphanumeric characters and spaces</li><li>Maximum length of 100 characters.</li><li>This parameter is applicable only for Corppass Login application. If provided for Myinfo Business application, the request will be rejected.</li></ul></td></tr></tbody></table>

### Supported authentication\_context\_type values

Currently, Corppass only supports one possible value:

<table><thead><tr><th width="289.6171875">Event</th><th>authentication_context_type Value</th></tr></thead><tbody><tr><td>General authentication</td><td><code>APP_AUTHENTICATION_DEFAULT</code></td></tr></tbody></table>

Additional values may be added in the future as new use cases arise.&#x20;

### Guidance on `authentication_context_type` usage

* If none of the predefined use cases above accurately describe your transaction, use the default value `APP_AUTHENTICATION_DEFAULT` for the general authentication use case.
* For general authentication to an e-service that performs a variety of actions, use the default value: `APP_AUTHENTICATION_DEFAULT`. This is expected to cover the majority of e-services.
* For more sensitive or transaction-specific actions that require step-up verification, a more specific `authentication_context_type` should be used.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.corppass.gov.sg/technical-specifications/corppass-authorization-api-fapi-2.0/integration-guide/1.-pushed-authorization-request-par-endpoint/authentication-context-parameters.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.