Skip to main content
J
jmehta1-Visitor
1-Visitor
March 21, 2018
Solved

Redirect user to other thingworx server.

  • March 21, 2018
  • 6 replies
  • 4112 views

Hi,

I have same user, home mashup and organization on server1.cloud.thingworx.com and server2.cloud.thingworx.com thingworx instance.

When user login from server1.cloud.thingworx.com/Thingworx/FormLogin/Organization it should login and redirected to server2.cloud.thingworx.com/Thingworx/Runtime/index.html based on some data table field.

Any idea how to achieve this?

 

Thanks

Best answer by supandey

Hi @jmehta my understanding is that redirects are handled by Tomcat configurations, I'm not aware if there is any possibility to transfer DataTable data after the user has completed the login process and is already in Server 1.

 

Sorry i am not really clear what exactly is your use case? I suppose it could be much easier to setup filters via the Tomcat to redirect users to specific URL patterns. Would help to have more context on this actually.

6 replies

S
supandey5-Regular MemberAnswer
5-Regular Member
March 22, 2018

Hi @jmehta my understanding is that redirects are handled by Tomcat configurations, I'm not aware if there is any possibility to transfer DataTable data after the user has completed the login process and is already in Server 1.

 

Sorry i am not really clear what exactly is your use case? I suppose it could be much easier to setup filters via the Tomcat to redirect users to specific URL patterns. Would help to have more context on this actually.

J
jmehta1-VisitorAuthor
1-Visitor
March 22, 2018

Hi @supandey, thanks for reply.

The use case is user will login to server1. After login we have to check whether this user's things is on server1 or not. If the user's thing is on server1 then show the Mashup. If user's thing is not on server1 then we have to redirect the user to server2. The user should not login again on server2.

S
supandey5-Regular Member
5-Regular Member
March 23, 2018

Wondering if this kind of use case could work with the custom authenticator. Also just a side thought on performance : may be such a use case also impact login time for the users, since at certain point you may have hundreds or even thousands of things which will need to be checked.

 

Would it not work to have these entities segregate based on projects/organisations? In that case you could use the different form logins for the users to direct them to different servers or mashups

Terms & ConditionsAccessibility statement