spring-projects / spring-projects/spring-boot
SAML2 autoconfiguration only supports unprotected private keys
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
Saml2RelyingPartyProperties.Signing and Saml2RelyingPartyProperties.Decryption only support unencrypted PEM format for the private key and certificate.
Instead, like other application properties used to provide private keys (e.g. SslProperties), it should support multiple formats, password protection, and ideally a trust store with multiple certificates.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading Saml2RelyingPartyProperties.Signing and Saml2RelyingPartyProperties.Decryption, then compare them with SslProperties, which is cited as a similar application-property implementation. Clarify the supported key and certificate formats, password protection, and trust-store behavior; done means SAML2 autoconfiguration supports the agreed set of protected and multi-certificate inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100