We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.
We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.
Thanks for collaborating with us!
Chef Automate frontend UI would support user authentication via JWT.
Link: https://jwt.io/introduction/
Basically the idea would be that we could configure Chef Automate with;
1. trusted header name to look for a JWT
2. a trusted issuer of those JWTs via a standardized URL
The JWT includes "claims" (aka attributes) about the user. So we could then map those claims to the Chef Automate username and even Chef Automate teams the way SAML config does now.
Thanks for contributing, Johnny. This idea has failed to capture the desired traction. We do not have immediate need to modify the existing IAM functionality. Am archiving it for now.
Attachments Open full size
Probably best to open that door to let us ingest our own.
Attachments Open full size
Seems Chef Automate does this within it's own calls after user logs in with currently supported methods.
Attachments Open full size