The following documentation outlines how to initialize the OAG Admin UI Console for the first time:
After following these steps and setting the cookie domains, OAG will redirect to the admin endpoint to log back in.
In the case of this issue, at this point instead of the login page, OAG displays a "System Error" with Tracking ID. The error indicates "An unexpected error occurred. This error has been logged." with no further details.
Other potential observations:
- When monitoring OAG Logs via Management Console, errors can be seen such as:
https://gw-admin.domain.domain_name/] error:[System Error] tracking ID:[6189f94875] details:[Could not find any default metadata entities in set [saml20-idp-hosted] for host [gw-admin.domain.<domain_name> : gw-admin.domain.<domain_name>]]
or
- When checking the OAG's Trusted Domains via Management Console, no entries are displayed.
- Okta Access Gateway (OAG)
As noted in the documentation, OAG does not allow using upper case when setting the OAG domains. The issue described here is the result of using upper case in the domain.
