Skip to main content
R
Rutger10-Marble
10-Marble
March 9, 2022
Solved

'Automatically update values when able' authorization issue

  • March 9, 2022
  • 2 replies
  • 2172 views

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?

Best answer by slangley

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
 

2 replies

P
PaiChung22-Sapphire I
22-Sapphire I
March 9, 2022

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.

R
Rutger10-MarbleAuthor
10-Marble
March 10, 2022

Thank you for your reply.

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

P
PaiChung22-Sapphire I
22-Sapphire I
March 10, 2022

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.

S
slangleyCommunity ManagerAnswer
Support
April 5, 2022

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
 

R
Rutger10-MarbleAuthor
10-Marble
April 6, 2022

Hi @slangley ,

 

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

Thanks for the follow up.

 

Kind regards,

 

Rutger

Terms & ConditionsAccessibility statement