-
Notifications
You must be signed in to change notification settings - Fork 142
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
Architecture docs #373
Comments
Agree, I would add a nice flow diagram of OIDC as well. |
I've got a very detailed description of the certificate request lifecycle in this doc I can repurpose for the "how a certificate request works" part of this https://docs.google.com/document/d/1PKAou7wEmEob4VOLq6rFlx5maOM5hkJ3XffZizfwdFw/edit The original doc was to discuss a proposal for #275 but I think the background information in it is probably worth adding in its own right |
I've been looking at OICD authentication flow is it correct the one to document is the Basic/Authentication flow? Am I correct saying that IDP redirects to fulcio, which then uses the ID token as issuer for the sign certificate? Or fulcio is not involved with authentication and just receives an ID token that validates with IDP? |
Work is complete |
Description
It takes a really long time to get started with Fulcio development because of the lack of architecture docs. The reader needs to spin everything up and look the the code to get the gist of how things work. I think we can make this much better with basic architecture docs including
The text was updated successfully, but these errors were encountered: