Skip to main content
Solved

IFS Cloud PSO Test Connection Failing


Forum|alt.badge.img+4

Hi,

When testing the connection in IFS Cloud (24R2) to PSO (24R2), it keeps failing. Upon initial configuration, the following error appeared. 

 

“Failed to connect to IFS Optimization server account Default. Error message was: 403 - Forbidden. The user IFSSCHEDULING and the parameters OpenIdAuthority, OpenIdClientId, UserNameClaim may need to be set up manually. Do you want to continue?”

 

I’ve reviewed other community posts that had similar errors and they were able to resolve it by whitelising the IP addresses. 

 

I’ve checked with the customer and they said that the environments are running on the same server and able to ping each other successfully. 

 

Are there any other issues during setup that can cause this error? In PSO, the parameters are blank. 

 

Best answer by roklde

Do you see the 404 message when browsing to https://<full-qualified-domain-name>/IFSSchedulingRESTfulGateway ? If yes, that’s fine. 

Seems like the IFS Cloud Server can’t reach PSO. So, as you said, check Firewall settings etc.

 

Best regards
Roman

View original
Did this topic help you find an answer to your question?

6 replies

Alexander Heinze
Superhero (Employee)
Forum|alt.badge.img+23

Here is a suggestion that ​@roklde gave in an internal chat:

 

That typically indicates an issue with the IAM Clients and/or IFSSCHEDULING and/or PSO Admin User. Try to re-configure the connection from scratch. Frist disable all active datasets and then disconnect the configuration. If that fails, go into PSO and clean the parameters OpenIdAuthority and OpenIdClientId. Further, remove the IFSSCHEDULING User. Delete IAM Clients IFS_automation, IFS_scheduling. Re-run the optimization assistant config and let it create the IAM client again.

 

Note: Before doing all of that make sure to set AllowAuthenticationGateway to true and have the PSO Administrator account details at hand! This will still give you direct access to PSO via the backdoor basic authentication login page at https:///IFSPSOWorkbench/Default/login?authGateway=true

 

The IFS_scheduling IAM client setup should look like this:

 


roklde
Superhero (Employee)
Forum|alt.badge.img+26
  • Superhero (Employee)
  • 748 replies
  • March 12, 2025

Hi Anthony,

are you sure that the configured PSO URLs are correct? For PSO on-premise and Azure deployments the URLs are:

https://<full-qualified-domain-name>/IFSSchedulingRESTfulGateway
https://<full-qualified-domain-name>/IFSPSOWorkbench

For Kubernetes deployments:
https://<full-qualified-domain-name>/pso/gateway
https://<full-qualified-domain-name>/pso/workbench

Best regards
Roman


Forum|alt.badge.img+4
  • Author
  • Do Gooder (Partner)
  • 9 replies
  • March 13, 2025

Hi ​@Alexander Heinze,

I followed the steps of disabling the datasets, deleting the IFSSCHEDULING user, removing IAM clients IFS_automation and IFS_Scheduling. 

In PSO, the parameters OpenIDAuthority and OpenIDClientId are empty. No values were inputted for the fields. 

The error still appears however when I rerun the configuration and the Test Connection continues to fail. 

@roklde, customer is on-premise and we can access PSO using - https://<full-qualified-domain-name>/IFSPSOWorkbench

 

Best,

Anthony 


Forum|alt.badge.img+4
  • Author
  • Do Gooder (Partner)
  • 9 replies
  • March 13, 2025

We will check further with customer as the PSO environment is now down and if there are any firewall issues. 


roklde
Superhero (Employee)
Forum|alt.badge.img+26
  • Superhero (Employee)
  • 748 replies
  • Answer
  • March 13, 2025

Do you see the 404 message when browsing to https://<full-qualified-domain-name>/IFSSchedulingRESTfulGateway ? If yes, that’s fine. 

Seems like the IFS Cloud Server can’t reach PSO. So, as you said, check Firewall settings etc.

 

Best regards
Roman


Forum|alt.badge.img+4
  • Author
  • Do Gooder (Partner)
  • 9 replies
  • April 3, 2025

Was an issue with the network. 

Thanks. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings