-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Give the users in "auth.administrators" the member node admin privileges #1816
Comments
I think this was a misunderstanding - what I meant was, the code already adds |
Aha! Makes sense now.
…On Thu, Feb 29, 2024 at 2:13 PM Matthew B ***@***.***> wrote:
Matthew said they had now. But this morning, I found they didn't when I
test the MN.delete method.
I think this was a misunderstanding - what I meant was, the code already
adds dataone.subject to the auth.administrators list at runtime. This
means that dataone.subject would then have the same privileges as the
auth admins currently do, but it appears the reverse is not true.
—
Reply to this email directly, view it on GitHub
<#1816 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB5QQDF3FJE5WGUATETYEWTYV6T2BAVCNFSM6AAAAABEAU2GGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSGA2TSOBZHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This has been completed via: Feature-1816: Metacat Admin MN Privileges (auth.administrators) |
This has been completed via Feature-1816: Metacat Admin MN Privileges (auth.administrators) - Resolve Broken Tests. Note: The previous PR left |
Now the users on
dataone.subject
have the member node admin privileges, such as delete, reindex. We decided that users inauth.administrators
should have the same privileges besides configuring Metacat instances.Matthew said they had now. But this morning, I found they didn't when I test the MN.delete method.
The text was updated successfully, but these errors were encountered: