- Newest
- Most votes
- Most comments
The issue you're experiencing with switching from Hosted UI to Managed Login in Amazon Cognito could be due to a few factors:
-
Timing: Changes to the branding version, including switching from Hosted UI to Managed Login, can take some time to propagate. It typically takes between 1 to 5 minutes for changes to take effect, depending on the domain type. In some cases, it might take up to an hour for the changes to be fully distributed.
-
Configuration: Ensure that you've followed all the necessary steps to set up Managed Login:
- Update the domain to use Managed Login under the "Branding version" setting.
- Delete any existing app client style for the Hosted UI.
- Create a new style using the branding designer and assign it to your app client.
-
Browser caching: Your browser might be caching the old Hosted UI pages. Try clearing your browser cache or testing in an incognito/private browsing window.
-
App client settings: Verify that the app client you've applied the new style to is the one you're using for authentication.
-
Domain configuration: Double-check that your domain is properly configured and active.
The issue with your Resource Server and ACM certificate is likely unrelated to the Managed Login not taking effect. However, you should resolve this separately to ensure your user pool is fully functional.
If after checking these points and waiting for a reasonable amount of time (up to an hour), the Managed Login is still not taking effect, you may need to contact AWS support for further assistance. They can help diagnose any potential issues specific to your user pool configuration or region.
Remember that switching between Managed Login and Hosted UI branding requires users to sign in again, so you may need to test with a fresh session.
Sources
Apply branding to managed login pages - Amazon Cognito
User pool managed login - Amazon Cognito
UpdateUserPoolDomain - Amazon Cognito User Pools
The branding designer and customizing managed login - Amazon Cognito
