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

documentation should take a stance / have guidance on trust bundle management #957

Closed
amoore877 opened this issue Jun 11, 2019 · 2 comments
Labels
help wanted Issues with this label are ready to start work but are in need of someone to do it priority/backlog Issue is approved and in the backlog stale

Comments

@amoore877
Copy link
Member

Overview and/or related READMEs / other documentation should have suggestions on management of trust bundle and certificate chain, including-

  • rotation option(s) for upstream CA and trust bundle
    -- related to Forcing Rotation of SPIRE Trust Bundle #928
  • on server side, what is expected in cert chain vs trust bundle. What must be in each, what should be in each, may be in each
  • on agent side, same for trust bundle
  • recovery options if trust bundle is compromised
    -- related to Forcing Rotation of SPIRE Trust Bundle #928
  • any additional specifics of above in regards to nested / federated SPIRE systems

suggestions do not necessarily have to be beyond high-level, and may also just link to industry guidance

such documentation helps both guide users of SPIRE and better direct the flow of future development and planning

@ajessup ajessup added the doc label Jun 11, 2019
@anvega anvega removed the doc label Dec 4, 2019
@azdagron azdagron added help wanted Issues with this label are ready to start work but are in need of someone to do it priority/backlog Issue is approved and in the backlog labels May 6, 2022
@github-actions
Copy link

This issue is stale because it has been open for 365 days with no activity.

@github-actions github-actions bot added the stale label Jul 13, 2023
@github-actions
Copy link

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Issues with this label are ready to start work but are in need of someone to do it priority/backlog Issue is approved and in the backlog stale
Projects
None yet
Development

No branches or pull requests

4 participants