SYN-5402: client certificates - #42
Merged
Merged
Conversation
mtichy-splunk
approved these changes
Jun 23, 2026
borisvalo
force-pushed
the
syn-5402-client-certificates
branch
from
June 24, 2026 08:45
c98f475 to
63ada57
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Resolves #SYN-5402
Before the change?
After the change?
ClientCertificate*models using public API JSON casing./certificates.certificateId, BrowseradvancedSettings.certificateIds, and API requestconfiguration.certificateIdmodel support.content,password, andvaluefields from captured request details.Pull request checklist
make testacc), and pasted in this PR (for bug fixes / features)Acceptance Test Output
Does this introduce a breaking change?