-
Notifications
You must be signed in to change notification settings - Fork 39
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
Revoking a certificate does not work #134
Comments
Just verified: I also doesn't work with any other certificate. |
I haven't tested it myself yet, but probably the fix is to change this line in
to
|
The error message changes now. It first gives a server error, an the labca log states: 2024-07-09T16:22:53.924487+00:00Z admin[1008]: 3 admin ntOk6wg [AUDIT] executing subcommand: got unacceptable revocation reason "5" |
Update: hardcoding the reason "superseeded" into the command does seems to be ok, but only does a dry run: gui-1 | 2024-07-09T16:29:07.703065+00:00Z admin[1022]: 6 admin 983jqAM [AUDIT] admin tool executing a dry-run with the following arguments: "bin/admin -config labca/config/admin.json revoke-cert -serial 7fb2d308a535cc7d5453b2c40fcd2456d364 -reason superseded" Adding "-dry-run=false" to the command does the trick, but not sure if this breaks something else. |
Thanks for the info! I will have a better look when I find some time
I expect it will be totally fine, but I need to have a better look at it |
You are probably right, so far it seems to be totally fine, except that the revoke reason is hardwired in the command file. |
This should now be solved in the v24.08 release |
Revoking a certificate in the gui does not work (nothing happens)
LabCA log states:
"'use
admin -config path/to/cfg.json revoke-cert -serial deadbeef -reason X
instead'"which seems to be a boulder error message about a malformed argument string in the revoke command.
The certificate to be revoked is one which was issued for the labca sever itself, but is not in use any more. Just in case this matters...
The text was updated successfully, but these errors were encountered: