Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X
Solved! Go to Solution.
The initial connection with the default appkey will be a connection only, there won't be context I think for the Admin user process to send a command back to the device that way.
If you give the default appkey perhaps permissions to run a specific registration service, it can pick it up that way.
Looks like you are missing visibility permissions for the new appkey user?
Everything else looks ok I think.
Registration could btw be initiated upon connection from the device side as well so you don't have to monitor for connected devices on a continuous basis.
Hi @PaiChung ,
Thanks for your fast reply.
The new appkey user is working fine, I'am having problems with the default appkey (initial one with no permissions).
Is it possible o set a remote property value and run a remote service while using an Administrator User in the Thingworx but having the device connected through an AppKey with no permissions ?
Considering your answer, any appkey user will need at least a visibility permission to allow connection between the device and the remote thing, is that right ?
Thank you very much.
The initial connection with the default appkey will be a connection only, there won't be context I think for the Admin user process to send a command back to the device that way.
If you give the default appkey perhaps permissions to run a specific registration service, it can pick it up that way.