"404 - Internal error" message rendered when new Cloud SWG admin logging in for first time
Article ID: 426684
Updated On:
Products
Issue/Introduction
New Cloud SWG admin created via the Enterprise Portal.
When the new admin tries to login, a "404 - Internal error" is rendered on the page instead of the Cloud SWG Portal.
Symptoms exist with different browsers and with standard/incognito mode.
Other admin users within the organisation can login without problems - seems to be specific to one user.
Environment
Cloud SWG Administration Portal.
Local Portal login.
Cause
Corrupted admin entry.
Resolution
Remove and recreate the problem admin user [email protected] with the following steps (requires a working admin that has access to both Enterprise and Cloud SWG Portals e.g. "admin A"):
- Using Admin A, login to the Enterprise console (EC) and navigate to Admin Management
- Remove Cloud SWG Super Admin role from the problem admin user [email protected] admin
- Under the Environments table -> Cloud SWG assign the Administrator role to [email protected] admin
- Using Admin A, login to Cloud SWG portal directly, navigate to Admin Management and delete the [email protected] admin
- Using admin A, inside the EC again, assign Cloud SWG Super Admin to [email protected] admin user.
- Finally, using the [email protected] user, try to login to Cloud SWG portal (https://portal.threatpulse.com) again and confirm all works.
Additional Information
Grabbing the HAR file when the issue happens shows that the admin user
- Accesses and logs in successfully to accounts.security.com Identity Provider
- is redirected to the Cloud SWG Portal login endpoint with an oauth2 code to 'https://portal.threatpulse.com/login/oauth2/code/oidc?code=#####' where
- Cloud SWG Portal responds with a '404 - Internal error'
The Cloud SWG Portal should take this oauth2 code, send to the Identity Provider via a backchannel and get an access token it can use but this process failed.
Feedback
