ADFS integration with Thingworx - Error : urn:oasis:names:tc:SAML:2.0:status:Responder

[Velkumar]

Hi Community,

We have trying to enable SSO on Thingworx using ADFS as IDP. We followed steps suggested in this link - Configuring Authentication with AD FS (ptc.com)

When we enable SSO on Thingworx, we are getting below error 

2024-06-29 04:54:29.694+0000 [L: INFO] [O: o.s.s.s.l.SAMLDefaultLogger] [I: ] [U: ???] [S: ] [P: ] [T: https-openssl-nio-443-exec-8] AuthNResponse;FAILURE;<<IP>>;<<RELYING_PARTY>>;https://<<ADFS HOST >>/adfs/services/trust;;;org.opensaml.common.SAMLException: Response has invalid status code urn:oasis:names:tc:SAML:2.0:status:Responder, status message is null__	at org.springframework.security.saml.websso.WebSSOProfileConsumerImpl.processAuthenticationResponse

Could someone help me to solve this issue

/VR

[PEHOWE]

@Velkumar ,

I took the error message you provided and did a search. This located Article - CS419861 - Not able to login to SSO enabled ThingWorx, SecurityLog shows Message not found in session error

 What URL are you using to start ThingWorx?  The article seems to say you are using "http:<localhost>:8080/Thingworx" You need to use "https://<localhost>:<secure Port>/Thingworx"
Let me know what you find.

[Velkumar]

Hi @PEHOWE 

This is not URL related issue. I'm accessing Thingworx using 443 secured port only.

/VR

[Velkumar · Accepted solution]

 Fixed issue with help of Support Ticket.

Disable Signing Certificate Trust Check in ADFS - java - Spring SAML Single Sign on ADFS Response failure because status message is null - Stack Overflow

Removed SAM-Account-Name from Claim

/VR