eBay / eBay/digital-signature-java-sdk
SignatureConfig - Lack of Setters
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 11
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Hi all,
After the latest changes made in version 1.1.0-RELEASE shouldn't SignatureConfig have setters for all the properties that one needs to set ?
Also why the default constructor is calling the addProvider ?
public SignatureConfig() {
Security.addProvider(new BouncyCastleProvider());
}
How one is supposed to leverage the new Signature if the SignatureConfig is a dummy one ?
Thanks in advance for your time.
Contributor guide
No contributing guide indexed for this repository
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 inspecting the SignatureConfig class and its default constructor. Determine which properties need setters and how provider registration should behave, then define the expected configuration and constructor behavior before changing the SDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100