SrisivakumarR.72127 (Customer) asked a question.
trying to redirect unassigned users to a custom error page which has been configured under customization-> application access error page. but this works for only the saml based apps not for the OIDC. is there any way to redirect the unassinged users to a custom error page for OIDC apps
Hello @SrisivakumarR.72127 (Customer) Thank you for posting on our Community page!
You are asking why custom error pages configured under Customization → Application Access Error Page work for SAML-based applications but not for OpenID Connect (OIDC) applications, and whether there is a way to redirect unassigned OIDC users to a custom error page.
The custom error page feature in Okta is primarily designed for SAML applications. OIDC applications handle unassigned user scenarios differently due to the OAuth 2.0 protocol flow, which returns an error response to the application rather than displaying an Okta-hosted error page.
Root Cause:
SAML applications receive error pages directly from Okta's server, so the custom error page setting applies. OIDC applications, by contrast, follow the OAuth 2.0 authorization code flow and return an error code (such as access_denied or unauthorized_client) back to the application's redirect URI. This means the error handling occurs on the application side, not on Okta's side, so the custom error page setting does not apply.
Official Workaround:
For OIDC applications, you must handle the unassigned user scenario at the application level:
Alternatively, contact Okta Support to verify whether your specific use case qualifies for any protocol-specific configuration options or to explore whether a policy-based approach might work for your scenario.
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
Hello @SrisivakumarR.72127 (Customer) Thank you for posting on our Community page!
You are asking why custom error pages configured under Customization → Application Access Error Page work for SAML-based applications but not for OpenID Connect (OIDC) applications, and whether there is a way to redirect unassigned OIDC users to a custom error page.
The custom error page feature in Okta is primarily designed for SAML applications. OIDC applications handle unassigned user scenarios differently due to the OAuth 2.0 protocol flow, which returns an error response to the application rather than displaying an Okta-hosted error page.
Root Cause:
SAML applications receive error pages directly from Okta's server, so the custom error page setting applies. OIDC applications, by contrast, follow the OAuth 2.0 authorization code flow and return an error code (such as access_denied or unauthorized_client) back to the application's redirect URI. This means the error handling occurs on the application side, not on Okta's side, so the custom error page setting does not apply.
Official Workaround:
For OIDC applications, you must handle the unassigned user scenario at the application level:
Alternatively, contact Okta Support to verify whether your specific use case qualifies for any protocol-specific configuration options or to explore whether a policy-based approach might work for your scenario.
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.