Hi, since we have rolled out SSO (SAML) in 7.6.1.2 users are getting Reload errors (error code 401 - see attachment), as well as occasional 500 Internal Server Error.

Has anyone seen this and what was the fix?

Any help would be greatly appreciated.

We also are seeing this after going to 7.6.1.3 and SSO . We have set up 2 aliases for logons.   Example might be:   maximoproduction/maximo or maximoproduction.abc.int/maximo.   We have found that the fully qualified url - maximoproduction.abc.int/maximo works more efficiently with far fewer of these pop ups and runs the KPI's off the start centers more efficiently.  Still seeking root cause.

------------------------------
Daniel Beyler
Allison Transmission

Original Message:
Sent: 12-13-2023 16:35
From: Steven Allen
Subject: Reload error and error 500 internal error

Hi, since we have rolled out SSO (SAML) in 7.6.1.2 users are getting Reload errors (error code 401 - see attachment), as well as occasional 500 Internal Server Error.

Has anyone seen this and what was the fix?

Any help would be greatly appreciated.

#MaximoUserGroups

------------------------------
Steven Allen
John Holland
------------------------------

Check the Load Balancer's session timeout, and Websphere LTPA token timeout. They are different to Maximo's session timeout but also have the same power of kicking you out mid-session. I have some notes about it in this post: https://blog.relia.app/2022/06/common-issues-when-setting-up-maximo-with-a-load-balancer/

We also are seeing this after going to 7.6.1.3 and SSO . We have set up 2 aliases for logons.   Example might be:   maximoproduction/maximo or maximoproduction.abc.int/maximo.   We have found that the fully qualified url - maximoproduction.abc.int/maximo works more efficiently with far fewer of these pop ups and runs the KPI's off the start centers more efficiently.  Still seeking root cause.

Hi, since we have rolled out SSO (SAML) in 7.6.1.2 users are getting Reload errors (error code 401 - see attachment), as well as occasional 500 Internal Server Error.

Has anyone seen this and what was the fix?

Any help would be greatly appreciated.

Hi Viet, i'm trying to go to the url you posted. I resulted in : 

This site can't provide a secure connection

blog.relia.app sent an invalid response.

IS there another way to read your advice?

Thanks in advance.

Kin dregards,

Hessel

Check the Load Balancer's session timeout, and Websphere LTPA token timeout. They are different to Maximo's session timeout but also have the same power of kicking you out mid-session. I have some notes about it in this post: https://blog.relia.app/2022/06/common-issues-when-setting-up-maximo-with-a-load-balancer/

We also are seeing this after going to 7.6.1.3 and SSO . We have set up 2 aliases for logons.   Example might be:   maximoproduction/maximo or maximoproduction.abc.int/maximo.   We have found that the fully qualified url - maximoproduction.abc.int/maximo works more efficiently with far fewer of these pop ups and runs the KPI's off the start centers more efficiently.  Still seeking root cause.

Hi, since we have rolled out SSO (SAML) in 7.6.1.2 users are getting Reload errors (error code 401 - see attachment), as well as occasional 500 Internal Server Error.

Has anyone seen this and what was the fix?

Any help would be greatly appreciated.