-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dns redirect after setup #622
Comments
Does anybody have registered his own domain and made DNS redirect to point to the Cloudfront URL and still have APIGateway portal working? Or does you only use on Cloudfront generated URL and give it for portal customers? I'm stuck with this sign in linkbutton problem. |
I managed to find that I need to set up Allowed callback URLs and also Allowed sign-out URLs in AWS Cognito to get authentication to work with custom domain and DNS redirection. Now sign-in and sign-out works with custom domain. However Users, Invites and APIs doesn't work until I use url prvovided by Cloudfront. With custom domain portal opens as empty and invite emails can not be sent |
I'm still stuck with this problem. I have portal in cloudfront url like https://b9kj2kop58o99w.cloudfront.net/ then I have DNS custom domain for example MyApiPortal123.com redirecting to it. I can register users and sign-in with them. However deployed API and Admins user lists etc are only shown when signed in with original Cloudfront Url.When opened via Custom domain APIs and other data stays empty. |
I found out that portals backend API should also be deployed manually in API gateway. |
Hello,
I have SAM deploy of developer portal up and running. Now I get custom domain Url and DNS to redirect to Cloudfront distribution of portal. When I browse to portal with that new domain and click sign in I get an error message "An error was encountered with the requested page." With direct Cloudfront distribution Url everything works. I Guess there is need to set custom domain name for portal. How this can be done?
The text was updated successfully, but these errors were encountered: