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

encryption done using symmetric or asymmetric key ? #1

Open
ananthmkh opened this issue Sep 3, 2018 · 5 comments
Open

encryption done using symmetric or asymmetric key ? #1

ananthmkh opened this issue Sep 3, 2018 · 5 comments

Comments

@ananthmkh
Copy link

Hi,
Can this policy be used for JSON complete payload encryption using symmetric (or) Asymmetric keys ?

@ozairs
Copy link

ozairs commented Sep 3, 2018

if your looking into the issue here. This only works on API Management V4.x; however, the majority of the configuration would be similar to API Connect V5 or V2018 but manual work is needed to migrate it over.

@ananthmkh
Copy link
Author

ananthmkh commented Sep 3, 2018

it worked for v5 for symmetric aes256 .. however, i used the shared secret key which was by default present in apimgmt domain related to oauth (webapi-oauth-token-ss).. the one I created using openssl is returning invalid key length for key wrap algorithm although i used same aes256-cbc

@thomas-burke
Copy link
Contributor

@kaushalygupta1991
Copy link

Hi Thomas,

I tried importing jwe encrypt policy in API Connect 5.0.8.4. But I am not able to run the policy. I am not able to find out Crypto Object to encrypt the data.

Please help me on what to do?

Thanks
Kaushalya Gupta

@thomas-burke
Copy link
Contributor

The crypto objects must be manually configured on the DataPower and referenced by name in the policy.

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

4 participants