You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some users will want to have the entire certificate chain provided to the authz policy. One option would be to expose the entire certificate chain as the identity, however, this might be overly complex for most use cases. An alternative would be to let the identifier include multiple keys in addition to input.identity. In the x509 parsing built-ins we just JSON serialize the Go struct: https://github.com/open-policy-agent/opa/blob/master/topdown/crypto.go#L22. We could do the same here.
Actual Behavior
Today, the TLS identifier only extracts the subject.
The text was updated successfully, but these errors were encountered:
Expected Behavior
Some users will want to have the entire certificate chain provided to the authz policy. One option would be to expose the entire certificate chain as the identity, however, this might be overly complex for most use cases. An alternative would be to let the identifier include multiple keys in addition to
input.identity
. In the x509 parsing built-ins we just JSON serialize the Go struct: https://github.com/open-policy-agent/opa/blob/master/topdown/crypto.go#L22. We could do the same here.Actual Behavior
Today, the TLS identifier only extracts the subject.
The text was updated successfully, but these errors were encountered: