-
Notifications
You must be signed in to change notification settings - Fork 25
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
How to do Payload Encryption with the SDK #19
Comments
I see this param in the src: |
Hi @jerryOkafor Sorry for the delay. See if this example helps you:
Also before using encrypted calls by sdk, public jwk set of sdk user must be registered on the Hyperwallet side, without this encryption won’t work |
Btw... thanks for your feedback about our documentation. We are working now finding the gaps and make our integrator's life easier. |
Thanks for your feedback, I think I am getting close. One more thing, the filed : |
CLIENT_PRIVATE_KEYSET_PATH - is the path where your private jwk keys set is located( it can be path to file or URL). The file located on /app/layer7/private-jwkset at github is encrypted because it contains private keys, so you can’t view it. In this example CLIENT_PRIVATE_KEYSET_PATH must be set with user’s own private jwk set, that can be easily generated. And the public part of that generated jwk set must be registered (you may contact our team to do it for you) at Hyperwallet side along with the REST user with which you make REST calls. HYPERWALLET_KEYSET_PATH - is the location of Hyperwallet public jwk keys set. For example: https://uat-api.paylution.com/jwkset |
@wmews-hw thanks for your support. I have tried to generate the jwkset using the following command : |
@wmews-hw after weeks of trial, I have succeeded in doing payload encryption using the Thanks in advance. |
@jerryOkafor could you confirm if it is related to this issue: #16 |
@wmews-hw I have confirmed, it does not relate to the above issue. I am still experiencing the issue at the moment. |
@jerryOkafor We will need more information to be able to reproduce this issue. Could you please give us a example how your request looks like? |
@wmews-hw I will give you access to the local test app so that you can run it and see the response. |
@jerryOkafor A new version of our sdk was released. Could you please confirm whether it fix or not the issue you've reported? |
ok, I will do that @wmews-hw. Thanks for your assistance. |
@wmews-hw I have a similar problem with Encryption and there is nothing said in the Hyperwallet documentation. Could you explain how to generate these private and public keys? I reckon it's easy when you know what you do :) Do I need server private key and based on this can I generate keys? |
@jerryOkafor Could your guide on how to generate and use this key? |
I am working on a project that uses the SDK, I have followed the guide on the Readme.md and when I make a call, I get Invalid credentials. I am thinking it is because of the payload encryption as stated here: https://portal.hyperwallet.com/docs/api/v3/overview/payload-encryption. When I informed my boss, he sent this link: https://github.com/hyperwallet/node-sdk/blob/master/test/utils/ApiClient.spec.js#L220. My confusion is this, the entire doc does not show how you can add encryption to the request that you make seamlessly. I don't know if anyone has done that before.
The text was updated successfully, but these errors were encountered: