AWS Verified Access error: Redirecting ...
Hi all
I'm following the workshop - verified access, https://catalog.us-east-1.prod.workshops.aws/workshops/dc70f5b4-a400-4c33-9a8e-c1b2baebbea4/en-US/aws-iam-identity-center/lab-3-device-trust-provider/3-9-test-application.
I used jumpcloud when I created Verified Access Device Trust Provider, https://catalog.us-east-1.prod.workshops.aws/workshops/dc70f5b4-a400-4c33-9a8e-c1b2baebbea4/en-US/aws-iam-identity-center/lab-3-device-trust-provider/3-4-ava-create-device-trust-provider.
I also added a redirect URI to your OIDC provider's allowlist as shown in https://docs.aws.amazon.com/verified-access/latest/ug/device-trust.html.
But I encountered an error as follows when I connected to the target url:
Redirecting...
what did I do wrong?
Thanks.
- 主题
- 网络和内容交付
- 语言
- English
- 最新
- 投票最多
- 评论最多
The "Redirecting..." error you're encountering suggests there might be an issue with the HTTP redirect configuration in your AWS Verified Access setup. To troubleshoot this, you should verify the redirect configuration by following these steps:
- Check the RedirectFrom URL: This is the URL you're trying to access.
- Verify the RedirectTo URL: This is where you should be redirected to.
- Compare the content at both URLs to ensure they match exactly.
- Confirm that the redirect is returning a 302 status code.
If the content doesn't match or you're not getting a 302 status code, there may be a misconfiguration in your setup.
Additionally, since you're using JumpCloud as your Device Trust Provider, ensure that:
- The public signing key URL in your Verified Access configuration is correct and accessible.
- The tenant ID for your JumpCloud application is correctly set in the Verified Access configuration.
- The redirect URI you added to your OIDC provider's allowlist is exactly correct, with no typos or extra characters.
If you've double-checked these configurations and are still experiencing issues, you may need to review your Verified Access instance settings, ensuring that all trust providers and Verified Access groups are properly set up and integrated.
Remember that AWS Verified Access evaluates application requests in real-time, so any misconfiguration in the trust providers or access policies could result in redirect issues. If the problem persists, you might want to check the AWS Verified Access logs for more detailed error information that could point to the specific cause of the redirect problem.
Sources
HTTP redirect issues - AWS Certificate Manager
Verified Access instances - AWS Verified Access
DeviceOptions - Amazon Elastic Compute Cloud
