diff --git a/source/partials/_authorize-errors.erb b/source/partials/_authorize-errors.erb index d671417..a2db5bc 100644 --- a/source/partials/_authorize-errors.erb +++ b/source/partials/_authorize-errors.erb @@ -1,14 +1,14 @@ -| HTTP status response code | Error | More information about your error | -|------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -|000| `unauthorized_client` | In rare circumstances, such as a security incident, One Login may prevent users from logging in to your service. If this happens, the error code `unauthorized_client` will be returned with the error description `client deactivated`. When your service receives this error, you must show the user a custom error page to explain that they cannot use your service at the moment and should try again later. | -|400| `Request is missing parameters XXXX` | The request has one or more of the following issues:
. You should [check you have included the correct parameters][integrate.replace-example-message], especially the `client_id`, `redirect_uri`, `response_type` and `scope` parameters. | -|000| `invalid_request` | The request has one or more of the following issues:
. You should [check you have included the correct parameters][integrate.replace-example-message], especially the `client_id`, `redirect_uri`, `response_type` and `scope` parameters. | -|000|`invalid_request - Request vtr not valid` | You've requested single factor authentication and identity information. To make a successful identity request, you must request two-factor authentication and the identity level of confidence, for example `Cl.Cm.P2`. | -|000| `invalid_scope` | The scope or scopes you have requested are invalid, unknown, or are not in the correct format.
You can read more about scopes in [choosing which user attributes your service can request][integrate.choose-user-attributes]. | -|000| `unsupported_response_type` | Your service is not registered for the requested `response_type`.
You must set the `response_type` to be code: `response_type=code`. | -|000| `server_error` | The GOV.UK One Login authentication server has experienced an internal server error. | -|000| `temporarily_unavailable` | If you're only making an authentication request (as opposed to requesting both authentication and identity), this error code means the GOV.UK One Login authentication server is temporarily unavailable, which might be caused by temporary overloading or planned maintenance.
Make your request again in a few minutes.

If you're making an identity request and you get this error, it means the identity proving and verification does not currently have capacity for this request. | -|000| `access_denied` | GOV.UK One Login returns this error in 2 scenarios.

The first scenario is that the identity evidence your user provided has a lower score than the identity confidence specified in your request. As a result, GOV.UK One Login could not return the medium level of identity confidence (`P2`) and instead returned a lower level of identity confidence.

If you’re using return codes, you will not receive this error. Instead, GOV.UK One Login returns an array of single letter `returnCode` values through the `userinfo` endpoint. Find more information on [understanding the return codes claim](/integrate-with-integration-environment/prove-users-identity/#understand-your-user-s-return-code-claim).

The second scenario is that the session in the user’s browser is unavailable. This can happen when your user’s cookies have been lost or your user changed browsers during the identity verification process. In this scenario, you should ask your user to log in again or restart the identity verification process. | +| Error | More information about your error | +|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| `unauthorized_client` | In rare circumstances, such as a security incident, One Login may prevent users from logging in to your service. If this happens, the error code `unauthorized_client` will be returned with the error description `client deactivated`. When your service receives this error, you must show the user a custom error page to explain that they cannot use your service at the moment and should try again later. | +| `request_is_missing_parameters` | The request has one or more of the following issues:
. You should [check you have included the correct parameters][integrate.replace-example-message], especially the `client_id`, `redirect_uri`, `response_type` and `scope` parameters. | +| `invalid_request` | The request has one or more of the following issues:
. You should [check you have included the correct parameters][integrate.replace-example-message], especially the `client_id`, `redirect_uri`, `response_type` and `scope` parameters. | +|`invalid_request - Request vtr not valid` | You've requested single factor authentication and identity information. To make a successful identity request, you must request two-factor authentication and the identity level of confidence, for example `Cl.Cm.P2`. | +| `invalid_scope` | The scope or scopes you have requested are invalid, unknown, or are not in the correct format.
You can read more about scopes in [choosing which user attributes your service can request][integrate.choose-user-attributes]. | +| `unsupported_response_type` | Your service is not registered for the requested `response_type`.
You must set the `response_type` to be code: `response_type=code`. | +| `server_error` | The GOV.UK One Login authentication server has experienced an internal server error. | +| `temporarily_unavailable` | If you're only making an authentication request (as opposed to requesting both authentication and identity), this error code means the GOV.UK One Login authentication server is temporarily unavailable, which might be caused by temporary overloading or planned maintenance.
Make your request again in a few minutes.

If you're making an identity request and you get this error, it means the identity proving and verification does not currently have capacity for this request. | +| `access_denied` | GOV.UK One Login returns this error in 2 scenarios.

The first scenario is that the identity evidence your user provided has a lower score than the identity confidence specified in your request. As a result, GOV.UK One Login could not return the medium level of identity confidence (`P2`) and instead returned a lower level of identity confidence.

If you’re using return codes, you will not receive this error. Instead, GOV.UK One Login returns an array of single letter `returnCode` values through the `userinfo` endpoint. Find more information on [understanding the return codes claim](/integrate-with-integration-environment/prove-users-identity/#understand-your-user-s-return-code-claim).

The second scenario is that the session in the user’s browser is unavailable. This can happen when your user’s cookies have been lost or your user changed browsers during the identity verification process. In this scenario, you should ask your user to log in again or restart the identity verification process. | diff --git a/source/partials/_token-errors.erb b/source/partials/_token-errors.erb index 1dc7f66..04f9cce 100644 --- a/source/partials/_token-errors.erb +++ b/source/partials/_token-errors.erb @@ -1,9 +1,9 @@ -| HTTP status response code | Error | More information about your error | +| Error | More information about your error | |------------------|--------------------------|---------------------------------------| -|000| `invalid_request` | The request is missing a parameter so the server cannot proceed with the request. This error may also be returned if the request includes an unsupported parameter or repeats a parameter.

Review your parameters and check they are supported and not repeated. | -|000| `invalid_client` | Client authentication failed, which could be caused by the request containing an invalid `client_id` or an issue in validating the signature of the `client_assertion`.

To resolve, check: