Skip to content
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

Split ZWESECUR into small pieces #2451

Open
jackjia-ibm opened this issue Nov 11, 2021 · 2 comments · May be fixed by #3718
Open

Split ZWESECUR into small pieces #2451

jackjia-ibm opened this issue Nov 11, 2021 · 2 comments · May be fixed by #3718

Comments

@jackjia-ibm
Copy link
Member

jackjia-ibm commented Nov 11, 2021

Currently ZWESECUR as a wholesome JCL which includes all permissions needed by Zowe core components.

If we can separate the JCL into small sections:

  • global security setup requirements
  • component level security setup requirements

Then we may leave the security definition into component level, and we can provide a standard way for any component/extension to request their own security setup.

The security definition from z/OSMF security descriptor could be a good standard we can follow. https://www.ibm.com/docs/en/zos/2.5.0?topic=zmfcg-creating-security-descriptor-files-security-configuration-assistant-task

With this change, we may be able to:

  • automatically generate ZWESECUR jcl based on what components the user decides to install and start
  • generate a combined security validation JSON for z/OSMF
@jackjia-ibm jackjia-ibm added the v2 label Nov 11, 2021
@MarkAckert MarkAckert added this to the v2 Ongoing milestone Jan 27, 2022
@jackjia-ibm
Copy link
Member Author

Vit created #2701 and could be related.

@jackjia-ibm
Copy link
Member Author

A little background what we are trying to achieve ZWESECUR.pptx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants