Hello, I’m developing an application with Angular 8 (And .Net framework), where I integrated an OKTA authentication layer, the okta client it’s SPA type, and it works perfectly in local, while serving the app from visual studio. But for some reason, after deploying the app to one of our servers (An…

For those who land on this post looking for web server configurations for their Angular apps, please check out the Deployment guide from Angular linked below. There are rewrite rule configurations for various web servers such as IIS, Apache, Nginx, etc. Angular Angular is a platform f…

Hello Andrea, No, I’m using “http” in both cases (Local and server). I have also these rules in the okta config file: pkce: false, cookies: { secure: false } Cheers.

I think the issues are on IIS, it could be breaking the params from the “url/callback#idToken=xxxxxxxxx”. Basically, that’s returning a 404, I’ve been trying using a rewrite rule to receive whatever url containing “callback”, and send to “url/callback”. Same result.

I’m still investigating about this, with no better results, tried several things on IIS config, different okta config. But similar result. The callback with id returned by Okta, is not getting processed properly by the app. Could be that the callback is not getting returned properly to the client si…

I would half wonder if its worth testing if this is specific to the hash fragment, or if you’d also have trouble receiving a query parameter at the callback route, but to do so, you would need to switch to using PKCE flow, since implicit flow will always use fragments. Is the Angular side handling …

Hey, I’m handling the token and all the okta layer in the Angular side, not in .Net. And about the hash fragment, I managed to remove the “#” (HashLocationStrategy), now the url for the callback it’s being sent, but apparently the response is not getting processed properly, this is the url where it …

I was using the angular okta library (@okta/okta-angular") and for the callback, the “OktaCallbackComponent” from the same library. That DOESN’T work with IIS, unless there’s a specific config required for that (Not present in any doc), I’ve tried using another library: “@okta/okta-auth-js”, and doi…

And Angular is correctly configured to use /login/callback as the callback route? Do you get any errors on the callback route?

Of course, it works locally served with visual studio (no errors), so it’s not an Okta/Angular config issue (Unless IIS requires some extra or specific config that I’m missing), but after removing the okta-angular library and not using the OktaCallbackComponent, using the code taken from this repo: G…

and the IIS server is configured to handle/host the callback route?

Callback redirect not working with angular app on IIS

Questions

andrea September 24, 2021, 12:21am 2

When deployed on IIS, are you using https?

While integrating angular app with okta i am getting this error:-

Post		Replies	Views
While integrating angular app with okta i am getting this error:- OAuth/OIDC	4	2176	May 15, 2023
Okta+angular when deployed in iis it is not routing properly Questions	3	1988	May 17, 2023
Angular on IIS - How? OAuth/OIDC	1	2447	October 25, 2023
No webpage was found for the web address: http://localhost:8000/login/callback OAuth/OIDC	3	1757	November 22, 2023
RedirectURI causes error in Angular Deployment Questions	11	6517	March 21, 2021

Callback redirect not working with angular app on IIS

Related topics