CarstenL.05291 (Trackunit A/S) asked a question.
redirect uri set though we still receive the error invalid request
Hello!
In our application called "oidc_aws_eks_external-lb_trackunit" which we use to OIDC auth against, we have set several redirect_uris, however the latest one seems to fail. We do not find much information in the logs of the app and our configuration is the same all around, so we wonder why the new entry fails.
The redirect_uri we've set for sign-in and sign-off is "https://argo.ops.awsapi.trackunit.com/oauth2/idpresponse" and the site we try to access is https://argo.ops.awsapi.trackunit.com/.
Error:
The 'redirect_uri' parameter must be a Login redirect URI in the client app settings: https://trackunit-admin.okta.com/admin/app/oidc_client/instance/0oa879yu6oWEoWA2V357*tab-general
Can you try to see if the request is somehow bad or if we're rate limited/capped or the like?
Thanks!
Hi @CarstenL.05291 (Trackunit A/S) , Thank you for reaching out to the Okta Community!
I'll start first with a cautionary note:
⚠️ Please note that this is a public forum and information posted here is visible to registered and unregistered users, so for your safety please redact your identifiable information like URLs and IDs.
As to your question - you should be able to check for rate limits being hit by going to your Okta Admin Dashboard → Reports → Rate Limits. You could also check the system logs by using keyword searches like "rate" or "rate limit".
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--------------------------------
The Okta Community Catalysts Program is now live. Collect online badges when you participate in the Okta Help Center Questions community. Learn more here.
Hello!
Thanks for letting us know not to post confidential information here, please advice on how to proceed covertly, as this is not optimal (I could not find any other means of support in out portal).
I looked over rate limits and that's not the issue - we also get paged whenever we reach any rate limits.
I believe the issue to be somewhere in the call/request toward Okta.
Kind regards
Carsten L. Jensen
SRE
On the bottom-right corner of the support site, you'll find the "Get Support" button. From there you can open a case or use the numbers listed to call the Support line and one of our Support Engineers will work with you to get things sorted.
Thank you! You may close this topic 🙂