Okta OIDC App Error "Does not match required pattern"
Last Updated:
Overview
This article covers the reasons behind the Does not match required pattern error that may occur with the redirectURI and initiateLoginUri properties when updating the OIDC applications from the Okta App Catalog using the Apps API and on the Okta Dashboard, along with how to resolve this error.
Applies To
- Apps API Endpoint
- OpenID Connect (OIDC)
- OAuth2.0
- Okta Integration Network (OIN)
Cause
When updating an OIDC app configuration from the App Catalog (OIN) using the Apps API and on the Okta Dashboard, it is important to ensure that a valid URL is provided, specifically when providing the redirectURI or initiateLoginURI.
Not providing a valid URL will cause the Apps API to produce the following error message in the response:
{
"errorCode": "E0000039",
"errorSummary": "Operation on application settings failed.",
"errorLink": "E0000039",
"errorId": "oaexP9eBzw4R66YUd4y0QA1yw",
"errorCauses": [
{
"errorSummary": "redirectURI: Does not match required pattern"
},
{
"errorSummary": "redirectURI: Is not an HTTPS URL. Valid example: https://www.okta.com"
},
{
"errorSummary": "initiateLoginUri: Does not match required pattern"
},
{
"errorSummary": "initiateLoginUri: Is not an HTTPS URL. Valid example: https://www.okta.com"
}
]
}
On the Okta Dashboard, it will produce the following error:
Solution
To resolve this issue, please ensure a valid URI is entered in the following format and that it uses HTTPS.
Example 1: In the Apps API request body
"redirectURI": "https://example.com/authorization-code/callback"
"initiateLoginUri": "https://example.com/login"Example 2: In the OIDC App settings on the Okta Dashboard
NOTE: If the Localhost URL is being configured and it is not HTTPS, Okta will produce the same error. So, the Localhost URL should be exposed to the internet, and the public URL configured to the OIDC app configuration, and ensure it is HTTPS.
