Skip to content

Add support for configuring WSS4J's USE_SINGLE_CERTIFICATE option #153

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

Conversation

cjsr
Copy link
Contributor

@cjsr cjsr commented Feb 17, 2020

Enable the manipulation of the parameter USE_SINGLE_CERTIFICATE, thus enabling the choice of using valueType X509PKIPathv1 in stead of X509v3.

… enabling the choice of using valueType X509PKIPathv1 in stead of X509v3.
@pivotal-issuemaster
Copy link

@cjsr Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@pivotal-issuemaster
Copy link

@cjsr Thank you for signing the Contributor License Agreement!

@gregturn gregturn changed the base branch from master to main April 7, 2021 15:50
@cjsr
Copy link
Contributor Author

cjsr commented Jun 16, 2021

@gregturn is there something I still need to do to get this pull request merged?

@cjsr
Copy link
Contributor Author

cjsr commented Nov 10, 2022

@gregturn could you please share with me what is still required of me to get this pull request merged? ;-)

… enabling the choice of using valueType X509PKIPathv1 in stead of X509v3.
@cjsr
Copy link
Contributor Author

cjsr commented Feb 5, 2025

Dear @corneil are there still changes required?
Best regards,
Jonas

@snicoll snicoll added the status: waiting-for-triage An issue we've not yet triaged label Feb 19, 2025
@snicoll snicoll changed the title Enable the manipulation of the parameter USE_SINGLE_CERTIFICATE, thus… Add support for configuring WSS4J's USE_SINGLE_CERTIFICATE option Mar 7, 2025
@snicoll snicoll added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Mar 7, 2025
@snicoll snicoll added this to the 4.1.0-M1 milestone Mar 7, 2025
@snicoll snicoll self-assigned this Mar 10, 2025
snicoll pushed a commit that referenced this pull request Mar 10, 2025
This commit allows to configure the `USE_SINGLE_CERTIFICATE` option,
which enables the choice of using valueType X509PKIPathv1 instead of
X509v3.

See gh-153
snicoll added a commit that referenced this pull request Mar 10, 2025
@snicoll snicoll closed this in 945b330 Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants