|
Description |
|
WS-Trust has been configured in EAM to integrate with the PingFederate identity provider. The mex address of PingFederate now contains a type=mex parameter, after which EAM appends the PartnerSpId parameter for the EAM Entity ID with a question mark rather than with an ampersand. This results in a 400 error message. *Steps to reproduce:* # On the SSO Configuration screen, configure the WS-Trust Configuration fields to integrate with a PingFederate enviroment # Attempt a web service login, for example from the HxGN EAM Connected application *Expected result* The PartnerSpId parameter for the EAM Entity ID should be appended with an ampersand and authentication should proceed. *Actual result* The PartnerSpId parameter for the EAM Entity ID is appended with a question mark and results in "_Server returned HTTP response code: 400_" |