-
Notifications
You must be signed in to change notification settings - Fork 593
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
origin_ca: remove the restriction of using API service keys #1161
origin_ca: remove the restriction of using API service keys #1161
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1161 +/- ##
==========================================
- Coverage 49.40% 49.31% -0.10%
==========================================
Files 127 128 +1
Lines 12290 12402 +112
==========================================
+ Hits 6072 6116 +44
- Misses 4840 4885 +45
- Partials 1378 1401 +23
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
changelog detected ✅ |
cc @maxnystrom |
The team has made strides in removing the restriction of only using the API user service keys for origin CA requests so we can now pass in any auth scheme the end user requires.
b54a5d9
to
8802b7f
Compare
This functionality has been released in v0.58.0. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Updates the documentation to align with the functionality updated in cloudflare/cloudflare-go#1161.
The team has made strides in removing the restriction of only using the API user service keys for origin CA requests so we can now pass in any auth scheme the end user requires.
Method updates:
CreateOriginCertificate
toCreateOriginCACertificate
OriginCertificates
toListOriginCACertificates
OriginCertificate
toGetOriginCACertificate
RevokeOriginCertificate
toRevokeOriginCACertificate
OriginCARootCertificate
toGetOriginCARootCertificate