Skip to main content
S
17-Peridot
Sathishkumar_C17-Peridot
17-Peridot
March 14, 2022
Question

Thingworx Mashup - Not Authorized for Read

  • March 14, 2022
  • 2 replies
  • 3914 views

For few mashups especially we used as popup, we are getting "Reason: 401 - Not Authorized for Read" in QA. But the same user role and permissions, we able to see that mashup in runtime as popup in Development Environment.

 

Its working after enable the "Design Time permission - READ" in QA.

 

My query is why its not appearing any permission related issues in Development? And, its appearing in QA even though the same permissions.

 

We are having an following thingworx instances in Development and QA environment.
Development Server - ThingWorx 9.1.9-b887
QA Server - ThingWorx 9.1.7-b776 

2 replies

V
24-Ruby III
VladimirN24-Ruby III
24-Ruby III
March 14, 2022
@Sathishkumar_C wrote:

... we are getting "Reason: 401 - Not Authorized for Read" ...

The only article mentioning this error is - "ThingWorx Analytics Things are not getting created in ThingWorx due to incorrect application key": https://www.ptc.com/en/support/article/cs271012 

S
17-Peridot
Sathishkumar_C17-PeridotAuthor
17-Peridot
March 14, 2022

Thanks for the information. Unfortunately, it's not useful in our case. We were not using thingworx analytics.  

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

Assigning Design Time - Read is the right way to solve this.

I've seen a few threads now on this, partly when users are removed from Composer users.

Not sure if the behavior is a difference between the versions, or if perhaps you have some collection permissions set in QA vs. Dev.

    S
    17-Peridot
    Sathishkumar_C17-PeridotAuthor
    17-Peridot
    March 22, 2022

    Yes. That user is not part of composer group. Its okay to assigning design time permission. But my doubt is the same level of permission and it is working fine with Dev environment.

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

    I understand, and unfortunately that is something I can't explain, but you could log a ticket with support for that.

    Terms & ConditionsCookie settingsAccessibility statement