Highlighted
Respected Contributor.
Respected Contributor.
70 views

Suddenly SAML integration stopped

Hi,

In our 8-months aged system suddenly SAML integration with ADFS has stopped. DB users can log-in but SAML users receive message: Invalid token. I double check time and data on all servers and ADFS. In IDM logs (idm-service) there are errors like:

2020-05-27T11:53:26.717+0200 ERROR [scheduler-3] com.hp.ccue.identity.ldap.load.RosterLoader - get unexpected exception
org.springframework.ldap.CommunicationException: ${hostname}:389; nested exception is javax.naming.CommunicationException: ${hostname}:389 [Root exception is java.net.UnknownHostException: ${hostname}]

 

Please help, Darek

0 Likes
2 Replies
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Hello,

You can try to download and reimport the ADFS server's federationmetadata.xml file. Possibly something was updated on ADFS and reimporting file and restarting pods can solve your issue.
Highlighted
Respected Contributor.
Respected Contributor.

Hi,
Thanks for advice. We did it but without success. But after enabling higher log level in IDM it appears that one of the files needed by IDM was physically damaged (Linux? :)). And Micro-Focus Service action was needed, after regenerating this file and re-applying SAML configuration to both sides system is now working.

Regards, Darek
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.