Random logout when accessing other ME application from same server
Issue:
We cannot access two or more ManageEngine products installed on the same server with the same machine name.
Root cause:
For example, if you have installed ServiceDesk Plus and Password Manager Pro in same machine and if you access ServiceDesk Plus via https://zylkercorp.com:8080/ and Password Manager Pro via https://zylkercorp.com:7272/ then this causes overlapping of cookies from SDP and PMP since both these URLs share the same domain zylkercorp.com.
Workaround:
If you cannot migrate other applications to new server machines, then you can check with your network admin and add CNAME entries like pmp.zylkercorp.com, sdp.zylkercorp.com , both pointing to the IP address of the zylkercorp.com server machine. Now you can access PMP via pmp.zylkercorp.com:7272 and SDP via sdp.zylkercorp.com:8080
New to ADSelfService Plus?
Related Articles
Random Logout fix (SD-113692)
Fix for 14202 to 14504: Download and place the logout_random_sd-113692_14202_14504.fjar in '<sdp>/fixes' folder Restart SDP service for the changes to take effect. To revert, undo the changes and restart SDP service.Logout Debug
Fjars for Logout DebugTo remove the apps banner from the Web application UI
Requirement: The requirement is to remove the apps banner from the below-mentioned place, thereby limiting users from downloading the mobile app and allowing the utilization of only the Web application. Procedure: >> Navigate to Admin > Page Scripts ...Step to change the Session-Timeout (Auto Logout)
Its is applicable from 11.0 version (11000 Builds) Please follow the steps below and change the mentioned file. 1. Shut down the application. 2. Navigate into <Supportcenter>/conf directory. 3. Open the file web.xml in an editor. 4. Search for the ...SAML | Common Workarounds: same entity ID in prod, test; hide "Logout from SAML"
1. Prod and Test have same entity ID: When restoring backup from production instance to create a test instance, the entity ID and and the redirect URL are same as the one in the production instance and we are not able to configure SAML in the test ...