cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

We are working to address an issue with subscription email notifications. In the meantime, be sure to check your favorite boards for new topics.

'Automatically update values when able' authorization issue

Rutger
8-Gravel

'Automatically update values when able' authorization issue

After upgrading from ThingWorx 9.1 to 9.2.6-b366 the 'Automatically update values when able' only works for administrators. 

When opening a mashup with as a non-admin user the application log states:

Not authorized for ServiceInvoke on ForwardEvent in PersistentSession

Unable to Invoke Service AddDynamicRemoteSubscription 

 

We verified Article CS346816 - https://www.ptc.com/en/support/article/CS346816 but didn't solve our problem/

 

Is there any change within 9.2.6 we need to consider?

1 ACCEPTED SOLUTION

Accepted Solutions
slangley
23-Emerald II
(To:Rutger)

Hi @Rutger.

 

From a review of the case that was opened, I see that adding the Visibility permission on EntityServices resolved the issue.  Please let us know if you agree.

 

Regards.

 

--Sharon
 

View solution in original post

5 REPLIES 5
PaiChung
22-Sapphire I
(To:Rutger)

Based on the error you need more permissions than the ones in the article.

I would add those ServiceInvoke calls as Runtime Execute overrides for your users.

Thank you for your reply.

Can you give me some guidance? Where should I change this? At Mashup or Thing?

PaiChung
22-Sapphire I
(To:Rutger)

I usually just look at the script/application log, because it will call out the Thing/Resource/Subsystem and the Service being invoked.

Or use the Developer tools, and check the lines in red.

Then I will go and set security on that entity and add an Override for that specific service to allow execution.

I'll basically repeat that until all the errors are gone.

slangley
23-Emerald II
(To:Rutger)

Hi @Rutger.

 

From a review of the case that was opened, I see that adding the Visibility permission on EntityServices resolved the issue.  Please let us know if you agree.

 

Regards.

 

--Sharon
 

Hi @slangley ,

 

Indeed, adding the Visibility permission on EntityServices resolved te issue.

Thanks for the follow up.

 

Kind regards,

 

Rutger

Top Tags