You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the AUTH_DEFAULT_ROLE parameter is set to "readable", one can view reports, profile etc.
I have set up a subject with the "readable" priviledges and a unique link is generated.
Then I change the AUTH_DEFAULT_ROLE parameter to status-only. The user with the link can only see the main page, but cannot access any other page (reports, profile, etc) . All the other pages ask for the API Secret, even though the parent page is the one with the token.
The issue is that the "readable" priviledge changes behaviour.
One would expect that the user with the token would be able to view reports, etc.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38420735-authentication-roles?utm_campaign=plugin&utm_content=tracker%2F2451736&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2451736&utm_medium=issues&utm_source=github).
The text was updated successfully, but these errors were encountered:
When the AUTH_DEFAULT_ROLE parameter is set to "readable", one can view reports, profile etc.
I have set up a subject with the "readable" priviledges and a unique link is generated.
Then I change the AUTH_DEFAULT_ROLE parameter to status-only. The user with the link can only see the main page, but cannot access any other page (reports, profile, etc) . All the other pages ask for the API Secret, even though the parent page is the one with the token.
The issue is that the "readable" priviledge changes behaviour.
One would expect that the user with the token would be able to view reports, etc.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38420735-authentication-roles?utm_campaign=plugin&utm_content=tracker%2F2451736&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2451736&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: