Hi Richard,

can you please verify if the scheduling app param called “BASE_WEB_CLIENT_URL” is setup correctly in FSM?

Best regards
Roman​​​​​​​

Hi Roman.  It is set up as a http connection and seems to be consistent with the endpoints. 

Param Category: Setup Table

Dataset ID: All datasets (we only have one in this environment)

All other functionality seems to be working as expected.

Richard

I assume that the User who opens FSM Webclient is setup as a PSO System User (see FSM Person record) and that user opens PSO Workbench through FSM Webclient. Is this assumption right?

Best regards
Roman 

Yes that is correct.

Richard

Are you using SSO?

We have not fully deployed SSO yet to web client users but some of the configuration parameters are in place.  APP PARAM FSM_AUTHENTICATION_METHODS are currently set to FSM and OIDC.

Ok. You can try to enable Webclient Debug Logging. Eventually this will log some more details on the issue. The steps to enable this are described in the OIDC Implementation Guide, see also here:

Hope that helps!

Best regards
Roman

Hi Roman.  We tried to execute the change above and are now just getting a ‘500 - Internal server error.’  I have created a case with OS to see if they can assist.  Thanks for you help.

Hi Richard,

I suppose there is an issue with the formatting in your web.config, if you now getting a 500 error. Did you try to put back the original web.config or double-check the syntax? 

Best regards
Roman

Hi Roman, yes we did revert back to the original version of the web.config and based on what we can see, there does not appear to be anything wrong with the syntax of the updated file.  We’ll wait for OS to pick up the case and work with them.  Thanks, Richard.