Skip to content
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

rejectedIdentifier: Better diagnosis #2091

Open
fubar-coder opened this issue Dec 6, 2024 · 0 comments
Open

rejectedIdentifier: Better diagnosis #2091

fubar-coder opened this issue Dec 6, 2024 · 0 comments
Assignees
Labels
enhancement needs triage Waiting for discussion / prioritization by team

Comments

@fubar-coder
Copy link

fubar-coder commented Dec 6, 2024

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

I had the problem that Step CA returned a urn:ietf:params:acme:error:rejectedIdentifier and the only error I got was The server will not issue certificates for the identifier. No further information was available and setting STEPDEBUG to 1 didn't log further information. My problem with this error was, that - even though Step CA returned the identifier to the client (Posh-ACME), Step-CA didn't even try to request the verification file for http-01 method.

I propose that the project returns much better (detailed) information when rejectedIdentifier gets returned.

Why is this needed?

It'd help with problem diagnosis - especially when working with Posh-ACME.

@fubar-coder fubar-coder added enhancement needs triage Waiting for discussion / prioritization by team labels Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement needs triage Waiting for discussion / prioritization by team
Projects
None yet
Development

No branches or pull requests

2 participants