We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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 ?
1.1.0-RELEASE
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.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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 ?
How one is supposed to leverage the new Signature if the SignatureConfig is a dummy one ?
Thanks in advance for your time.
The text was updated successfully, but these errors were encountered: