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
{{ message }}
This repository was archived by the owner on Sep 21, 2022. It is now read-only.
The current POST /revocations is not compliant to the corresponding RFC 7009.
Also it's currently unknown why there are multiple revocation types. This implicit knowledge needs to get clarified and made explicit with proper documentation. Alternatively, the implementation needs to get fixed (which will make breaking API changes unavoidable).
The text was updated successfully, but these errors were encountered:
@gargravarr thx for the link. unfortunately it's not clear why there are multiple revocation types and whether or not there are Zalando-internal or external requirements for this. The spec certainly doesn't know them.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The current
POST /revocations
is not compliant to the corresponding RFC 7009.Also it's currently unknown why there are multiple revocation types. This implicit knowledge needs to get clarified and made explicit with proper documentation. Alternatively, the implementation needs to get fixed (which will make breaking API changes unavoidable).
The text was updated successfully, but these errors were encountered: