Add the GetCACaps operation handling to the SCEP servlet #541
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the
GetCACaps
operation to the SCEP servlet. TheGetCACaps
operation is defined in the new SCEP drafts and it should allow Dogtag to support SCEP clients that require it (or, as an example, we found out that some clients switch to using deprecated hash / encryption algorithms when they don't receive proper response from this operation).I went through the current SCEP implementation in Dogtag to try to determine which features are exactly supported and which not. If I understood things correctly, Dogtag doesn't support AES in SCEP, certificate renewal (I am about to try to implement this though) and CA cert rollover (the
GetNextCACert
operation). Other features listed in the draft are supported and printed as the operation response in a simple text form, following the draft specification.This is the output of calling this operation (using curl):
I am ready for your suggestions, thank you for considering this PR!
Update: I found out that the HTTP POST requests are not properly handled, I opened a separate PR #542 for this.