Okta Access Gateway Application Creation Fails Without a Subdomain in the Public URL
Last Updated:
Overview
Okta Access Gateway (OAG) fails to create an application when the public URL lacks a subdomain. Administrators must modify the public URL to include a valid subdomain to resolve the issue. When saving the application, Okta logs a specific error message and generates a Server Side Error in the user interface.
message:Failed generating cookieDomain, developerMessage:Check that valid relaydomain is being used
2025-05-29T15:45:42.000-04:00 oag-admin.domain.tld ACCESS_GATEWAY WEB_CONSOLE handling service exception: com.icsynergy.spgateway.service.NotFoundException Error: com.icsynergy.spgateway.domain.SPGWError(type:NotFoundException, status:0, code:SPGW_NOT_FOUND, message:Failed generating cookieDomain, developerMessage:Check that valid relaydomain is being used, errors:[:], context:null)
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Access Gateway (OAG)
Cause
The application public URL requires a subdomain in a Fully Qualified Domain Name (FQDN) format. A root domain format like <companyapp.com> causes the failure, whereas a format with a subdomain like <app.company.com> functions correctly.
Solution
How is the public URL subdomain error resolved?
Navigate to the application settings, modify the public URL to include a valid subdomain, and save the configuration.
- Navigate to the application settings.
- Modify the public URL to include a valid subdomain.
- Save the application.
NOTE: Administrators can use www as a subdomain, but Okta does not recommend this configuration. Users must include the www prefix in the URL when accessing the application, otherwise Okta Access Gateway returns an Unknown host 400 status code error page.
