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

Add guidance on tickets for UAA and Shibboleth #2464

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

pburkholder
Copy link
Contributor

Changes proposed in this pull request:

  • Add guidance on tickets for UAA and Shibboleth

security considerations

Need to determine if public tix for routine updates are OK

@pburkholder
Copy link
Contributor Author

Slack conversation on this:

Mark Boyd (cloud.gov - Alexandria)
as for where to create tickets, only create them in private if you're worried about broadcasting vulns

otherwise, you can create them on the bosh release repos

the important thing really is to notify me that they exist and i'll tag them appropriately so they don't get lost in the ether

@pburkholder
Copy link
Contributor Author

@Chiakao @JoeLindsey87 @seanmbazemore @wz-gsa -- This WIP PR adds a few hints to ConMon on what to do with findings for UAA and Shibboleth. Should we fix the conflicts and merge, or close unmerged?

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

Successfully merging this pull request may close these issues.

1 participant