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
I was failing to get a cert when requesting a cert for foo.example.com when the zone being managed by powerdns was .example.com. We're using powerdns with a custom auth proxy and it gives a 403 if you try to manage a zone that's not matched to the api key.
I accept that this isn't the normal flow of things for your average powerdns api user, but it was easily fixed by a check for 403 in _handle_http_error. Is this something you'd consider a patch for?
The text was updated successfully, but these errors were encountered:
I was failing to get a cert when requesting a cert for
foo.example.com
when the zone being managed by powerdns was.example.com
. We're using powerdns with a custom auth proxy and it gives a 403 if you try to manage a zone that's not matched to the api key.I accept that this isn't the normal flow of things for your average powerdns api user, but it was easily fixed by a check for 403 in
_handle_http_error
. Is this something you'd consider a patch for?The text was updated successfully, but these errors were encountered: