Access Control for experiences

[mwodarz_INNEO]

I am looking for a solution to control access to different experiences.

For example: a company has one experience service running, but using this in different teams. Each team should store the own experiences, but shouldn't see the experiences from the other teams.

Working only with Thingmarks isn't that secure and not a good solution for this.

It would be fine if Studio experiences provide access control like expert capture assets (simple and transparent).

Also a solution without any code in every experience would be useful.

What are your ways to handle these?

Thanks in advance for the replies.

Cheers

Marco

[JG_8568288]

Good point, solution would be very appreciated.

[sdidier]

Hello Marco,

In Vuforia Studio, we can setup an authentication for each Experience.

More details here :

http://support.ptc.com/help/vuforia/studio/en/#page/Studio_Help_Center%2FConfigInfo.html%23

This authentification allows connection from any user defined in ThingWorx.

It needs some Javascript in ThingWorx in a specific service code to check user is defined in a specific user group.

In Vuforia Studio side, check this Service to see if user is defined in a specific group to allow access or not.

A specific UI and call to this Javascript function to go outside Experience.

https://community.ptc.com/t5/Vuforia-Studio/How-to-re-scan-a-Thingmark-automatically-adding-JS-code-not/td-p/513619

From my point of view, it is the easiest and simple solution today, to do that.

Best regards,

Samuel