search

Layer7-Community / graphman-client

This repository contains a Postman collection, a Node.js CLI application, sample queries for the CLI, and GraphQL schemas for the Graphman API.
Other
7 stars 5 forks source link

explode p12 file not readable #70

Closed muemi03 closed 2 months ago

muemi03 commented 2 months ago

I just tested to export and explode a key, and then read it by openssl. This has worked fine, when doing it with the previous graphman-client version, but it does not anymore for me with version 1.3.00 .

old version commands: graphman.sh export using keyByAlias --variables.alias \<key-alias-name> --output key-old.json graphman.sh explode --input key-old.json --output key-old --explodeKeys openssl pkcs12 -in key-old/keys/\<key-alias-name>.p12 -nodes -nocerts -passin pass:\<l7-passphrase>

new version commands: graphman.sh export using keyByAlias --variables.alias \<key-alias-name> --gateway --output key-new.json graphman.sh explode --input key-new.json --output key-new --options.level 1 openssl pkcs12 -in key-new/keys/\<key-alias-name>-\<keystore-id>.p12 -nodes -nocerts -passin pass:\<l7-passphrase>

last command fails with wrong password

Please check Thanks

muemi03 commented 2 months ago

Sorry. Completely my fault !!! using new client with old gateway .... error reason: passphrase header name has changed and header value now get base64 encoded. after adopting to the "old" way in doing things, everything is working in this regard. These changes will be reverted as soon we upgraded our gateways ! Closing now.