MarcoH.63697 (Customer) asked a question.
So, I have used OKTA to login into a web app like a year ago.
When revisiting that code, it now simply shows a CORS error when trying to sign in.
I have checked, double checked and tripple checked all the resources google could come up with, up to and including page 2 and 3 even. I am 99,9% certain I should have all in order.
To give a blank slate: I started a new project and followed THIS guide to the teeth: "Build Secure Login for Your Angular App | Okta Developer"
I made sure trusted origins had the CORS enabled option checked and yet: I am still getting CORS error no matter if tested on localhost or published as a web app.
I have run out of ideas really and need someone from OKTA to see what is wrong with my configuration. I don't seem to have the rights to open a support ticket it seems,... so this is all the option I seem to have for now.
Turnes out that all I had to do was change the redirect urls again. It removed the "s" from "https".
Since it worked a year back and I just touched it again today, I now wonder why that changed itself (?). ALL listed URLS had that happen to them. There is no way this could have worked before,... very strange.