Skip to main content
imshaikh5-Regular Member
5-Regular Member
September 18, 2017
Solved

installing and configuring Thingworx with H2 database

  • September 18, 2017
  • 5 replies
  • 3345 views

I am using Thingworx 8.0 with H2 db and navigate framework 1.5.

I am trying out this configuration for Thingworx SSO.

Here are some more details about it,

- I am using PingFederate as an IDP

- if i am disabling SSO in platform-settings.json file then Thingworx login works fine but if we enable it in platform-settings.json file then its giving some issue and i am not even able to see PingFed login page.


I am not able to open url http://localhost:8090/Thingworx/​​.

     - here 8090 is the port configured for Apache Tomcat.

It is giving some error, you can see attached log file for more information.

Any help would be really appreciated here.

Thanks,

Imran

Best answer by posipova

Jugding by the error, it is what it is - the failed signature is causing Idp not to work. It's trying to verify trust of the signature using keys found in the configured keystore. You may try to import the public certificate of the metadata signature (or of its CA + intermediate CA's) to the keystore. It should pass then unless it's expired.

5 replies

supandey5-Regular Member
5-Regular Member
September 18, 2017

Hi Imran, have you checked the Application Log and the Tomcat's catalina log for detail. The zip attached to your question doesn't seem to contain any error against the authentication issue.

imshaikh5-Regular MemberAuthor
5-Regular Member
September 18, 2017

Hi Sushant,

I have attached ApplicationLog and Catalina log with this reply.

I am getting some 'Signature trust establishment failed for metadata entry' error in ApplicationLog.

Please let me know if you need any more details.

Thanks,

Imran

posipova20-TurquoiseAnswer
20-Turquoise
September 18, 2017

Jugding by the error, it is what it is - the failed signature is causing Idp not to work. It's trying to verify trust of the signature using keys found in the configured keystore. You may try to import the public certificate of the metadata signature (or of its CA + intermediate CA's) to the keystore. It should pass then unless it's expired.

Terms & ConditionsAccessibility statement