-
Notifications
You must be signed in to change notification settings - Fork 143
Updating configuring-security.md #4762
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
base: master
Are you sure you want to change the base?
Updating configuring-security.md #4762
Conversation
Signed-off-by: arooshlele <[email protected]>
|
😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.
Need help? Contact the Doc Squad in the #zowe-doc Slack channel. |
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.
This is a good topic to improve, but I don't think it will be seen or understood in the place you put your info.
-
you have only made a v3.0.0 doc, but if you're trying to update documentation people will see, you need to do a v3 latest doc, and then to get the widest audience, update all the versioned_docs (like this, but all the others too)
-
The page you've edited is in the context of action items for admins to do to set up the zowe server security setup. You've added a section talking about zowe user security setup. I just don't think this is in the right section.
I'm not sure there is a good place to put this currently, you may need to create a new page to better represent this, and reorg the more visible pages to point ot it.
Check out
https://github.com/zowe/docs-site/blob/master/docs/user-guide/address-security-requirements.md
it (and the page you edited) reference
At the bottom of that, there's a section about users.
As it is, that page saying 'users' at the top is misleading, because most of the page is about permissions of the STC account, not users. The bottom of the page is however about users.
I suggest
- renaming https://github.com/zowe/docs-site/blob/master/docs/user-guide/assign-security-permissions-to-users.md to 'assign security permissions to STC accounts'
- make a page that's actually about users, and populate it with content like you wrote, among other things.
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.
Sean's comments seem very pertinent.
I also left some comment re: minor edits.
| :::note | ||
| For the users of Zowe who are not database administrators, administrators, or superusers, the minimum access requirements are as follows: | ||
|
|
||
| - z/OSMF Access: The user must be a member of the IZUUSER group (membership in IZUADMIN is optional and provides additional privileges if required). |
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.
I'd suggest moving the parenthetical into a sub-bullet (and removing the parentheses)
| For the users of Zowe who are not database administrators, administrators, or superusers, the minimum access requirements are as follows: | ||
|
|
||
| - z/OSMF Access: The user must be a member of the IZUUSER group (membership in IZUADMIN is optional and provides additional privileges if required). | ||
| - USS Access: The user ID must have an ** OMVS segment defined to interact with UNIX System Services. |
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.
Should the asterisks be in backticks? Like: "... have an ** OMVS segment defined ... "
|
|
||
| - z/OSMF Access: The user must be a member of the IZUUSER group (membership in IZUADMIN is optional and provides additional privileges if required). | ||
| - USS Access: The user ID must have an ** OMVS segment defined to interact with UNIX System Services. | ||
| - Dataset and USS Permissions: The user requires the standard RACF/ACF2/Top Secret permissions to access datasets and USS files. |
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.
Data set should be two words.
Describe your pull request here:
As discussed with @DivergentEuropeans Lenny, a Note related to Security permissions is added into this file.
List the file(s) included in this PR:
configuring-security.md
After creating the PR, follow the instructions in the comments.
CC: @ArooshLele @DivergentEuropeans @1000TurquoisePogs @gauravs-20