-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Organization restricted datastore #4892
Conversation
…anization-restricted-datastore
…anization-restricted-datastore
Changes thus far LGTM, but I think another change is required: datasets reported by that datastore should be ignored (probably with command line warning) if they are not for its organization |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Backend LGTM.
Sorry, one more concern: should the datastore be visible to users of other organizations? Maybe adapt the accessQuery? (Or if that causes trouble, at least hide it from the upload form dropdown menu? The refresh button should probably also not talk to datastores specific to other organizations)
URL of deployed dev instance (used for testing):
Steps to test:
onlyAllowedOrganization
to random id => upload to that ds should failonlyAllowedOrganization
to organization id => upload to that ds should work when logged in as user of that orgIssues:
[ ] Updated documentation if applicable[ ] Adapted wk-connect if datastore API changes