Skip to content
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

Make crypto provider configurable #2329

Open
dulanjal opened this issue Oct 25, 2019 · 0 comments
Open

Make crypto provider configurable #2329

dulanjal opened this issue Oct 25, 2019 · 0 comments

Comments

@dulanjal
Copy link

dulanjal commented Oct 25, 2019

Description:
Currently, BouncyCastle ("BC") crypto provider is hardcoded in org.wso2.carbon.core.util.CryptoUtil (E.g. Refer [1]), which is used for conducting internal encryption tasks such as OAuth2 token encryption. We should check the feasibility of making this configurable in order to allow use of FIPS 140-2 compliant crypto providers (E.g. "BCFIPS").

[1]

encryptedKey = cryptoService.encrypt(plainTextBytes, algorithm, CRYPTO_API_PROVIDER_BC);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant