Skip to main content

A customer is having problems when using OIDC to access the FSM Web Client. The customer has checked their SSO environment and believes it to be correct. However, we are getting a 403 error when trying to use OIDC.

From outside their  network, I can get to the FSM web client landing page:

 

If I use FSM authentication, I can log in OK:

 

However, if I select “Use OIDC Login” on the landing page, I briefly see the redirect to the Microsoft page:

 

before being bounced back to the root page of the server with a 403 error:

 

Does anyone have ideas/suggestions as to what might be wrong or how to troubleshoot this further?

Steve

@Sajith D hope you can help

hi @Steve Hurst ,

We will need to see how the redirect URL’s are setup in Azure App registration to figure out where the problem is. Looking at the images it looks as if the Azure is not directing the traffic correctly but can’t be sure without having a look at what is defined.

Cheers.

Hi @Sajith D 

Many thanks for the reply. I have this information now, and so will send it to you directly rather than post it on an open forum.

Thanks

Steve

@Aaron.Sleight @Jon Reid is there any other pointers that can be given for this issue?

You need to set up the redirect urls in appsettings.json to the *external* urls if there is a reverse proxy.   This can be specified in the installer.   Since the installer runs on the app server it is not directly aware if the external url is different.  Also you might have an uppercase/lowercase issue - the urls need to be consistent in case.

Reply


Terms & ConditionsCookie settings