a get request from postman returns 200 after configuring aws cognito twitch OIDC. However when I do the get request from the app on twitch i get CORS. I suspect this is the problem has to do with callback url or extension allowlist?
Should this be filled out? I am using twitch to host my front end.
twitch as idp was configured using the docs and is geetting 200 but this page i left blank do i need to put anything here?
I understand the <a href=" instead of get request. But on my backend cognito where I setup OIDC do i have to add a redirect there?
Here should I be ticking twitch and adding the twitch /authorize to the callback here? Or I dont need to fill this out since twitch is IDP?
I understand redirect_irl handles the authentication. But once authenticated you can enter a callback url. I will check some other code examples maybe I can get a clue from there.
Thank you for reply again.
I see where I got confused. I will test it using the cognito handler thank you again
but other terms like “Redirection URI”, “Redirection URL”, “Redirect URI”, “Redirect URL”, “Callback URL” and “Callback URI” etc. are all used interchangeably, some because in protocol fields the term gets shortened to things like redirect_uri , others because of inherited legacy terminology from similar protocols that pre-date OAuth 2.0.