-
Notifications
You must be signed in to change notification settings - Fork 47
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
Improve description of Reader role #7583
Comments
@idlewis When the REST connector feature is enabled, you can configure management roles for your Open Liberty server. These roles grant users and groups that are defined in a user registry access to select administrative REST APIs. You can use any supported user registry.
The following example maps users and groups that are defined in a basic user registry to the reader and administrator roles. |
One further comment. This sentence from your draft: |
Quick question based on your comment above. Does the role determine the kind of access you have to a given API, or does the API itself determine which roles can access it? The way you drafted the sentence suggests that the API determines which roles can access it. Is that the case? CC @dmuelle |
The administrator role can access all APIs. |
Yes, I think that is accurate. |
Would this be ok? CC @dmuelle |
I think that should be okay. Could you update the draft so that I can review it in context? |
7583-Improve description of Reader role-2 #7583
@ramkumar-k-9286 - looks good, please open a PR to staging |
https://openliberty.io/docs/latest/reference/feature/restConnector-2.0.html
This pages describes Liberty's
reader
user role, but doesn't make it sufficiently clear the level of access that this role provides.Where the page currently states:
Users who are in the reader role can monitor the server ...
I'd like to change it to say something like:
Users who are in the reader role have the same permissions to monitor the server as the users in the administrator role ...
@mingcyu
@leochr
Thoughts welcome on the wording
The text was updated successfully, but these errors were encountered: