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
{{ message }}
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.
Information stored in the UserInfo collection, which includes accessGroups and email, is visible to any user as long as they have an authentication token.
Steps to Reproduce
Go to the explorer, set your access token and query the UserInfo table. All users' info are displayed
Current Behaviour
All users' info is displayed
Expected Behaviour
Only info limited to the current user should be displayed (if we want to limit its visibility)
Extra Details
Here you should include details about the system (if it is unique) and possible information about a fix (feel free to link to code where relevant). Screenshots/GIFs are also fine here.
The text was updated successfully, but these errors were encountered:
When I query our production instance with the following command: curl -X GET --header 'Accept: application/json' 'https://scicat.ess.eu/api/v3/Users?access_token=<ACCESS_TOKEN>
and I get: "error":{"statusCode":401,"name":"Error","message":"Authorization Required","code":"AUTHORIZATION_REQUIRED"}}
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Name
userInfo permissions
Summary
Information stored in the UserInfo collection, which includes accessGroups and email, is visible to any user as long as they have an authentication token.
Steps to Reproduce
Go to the explorer, set your access token and query the UserInfo table. All users' info are displayed
Current Behaviour
All users' info is displayed
Expected Behaviour
Only info limited to the current user should be displayed (if we want to limit its visibility)
Extra Details
Here you should include details about the system (if it is unique) and possible information about a fix (feel free to link to code where relevant). Screenshots/GIFs are also fine here.
The text was updated successfully, but these errors were encountered: