-
Notifications
You must be signed in to change notification settings - Fork 26
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
Comments
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. |
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 |
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 |
The crypto objects must be manually configured on the DataPower and referenced by name in the policy. |
Hi,
Can this policy be used for JSON complete payload encryption using symmetric (or) Asymmetric keys ?
The text was updated successfully, but these errors were encountered: