Skip to main content
S
SDeLausnay3601-Visitor
1-Visitor
April 25, 2019
Solved

Control room dashboard without session timeout

  • April 25, 2019
  • 2 replies
  • 1609 views

We have an application which needs to run in the control room of the plant. This screen should show 24/7 without having to re-login by the operators. I know we can set the Session Idle time for all the users, but this is not preferred because also other users can access the application (and other application on the same platform) where people can have the session timeout to not be logged in without knowing. 

 

I found a post to track user activity in the mashup and then run a timer to logout users actively but this also not ideal because we then need to do it for every mashup/application we have build. 

 

 

Thanks for helping out. 

 

 

Best answer by serler

Instead of Login via username & password, you can try to log in to the Mashup using an AppKey.

You can append the appKey as part of the URL:

http://<ThingWorxServer>:<ThingWorxPort>/Thingworx/Runtime/index.html?appKey=<YourAppKeyHere>&x-thingworx-session=true#mashup=<mashup_name>

 

Note: to do so "Allow Application key as URL Parameter" must be activated in the configuration of the PlatformSubsystem.

2 replies

S
serler5-Regular MemberAnswer
5-Regular Member
April 25, 2019

Instead of Login via username & password, you can try to log in to the Mashup using an AppKey.

You can append the appKey as part of the URL:

http://<ThingWorxServer>:<ThingWorxPort>/Thingworx/Runtime/index.html?appKey=<YourAppKeyHere>&x-thingworx-session=true#mashup=<mashup_name>

 

Note: to do so "Allow Application key as URL Parameter" must be activated in the configuration of the PlatformSubsystem.

S
serler5-Regular Member
5-Regular Member
April 25, 2019

Alternatively you can access the mashup without activating the "Allow Application key as URL Parameter" checkbox, by using a custom header in the browser with AppKey.

 

This can be achieved for example in firefox by using the "modify header value" extension. The header configuration would then look like the following:

 

    Terms & ConditionsAccessibility statement