-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add info on encrypting requests and disabling signature validation in sandbox to DESCRIPTION.md #117
Conversation
DESCRIPTION.md
Outdated
@@ -500,6 +500,30 @@ If you get an error telling you "The request signature is invalid", please check | |||
- You use the data to sign to create a SHA256 hash signature. | |||
- You have base64 encoded the SHA256 hash signature before adding it to the request under `X-Bunq-Client-Signature`. | |||
|
|||
**Note:** Though request signing is a must on production, you can choose to disable it on sandbox to simplify the testing. Here's how it works: | |||
|
|||
1. Set the `X-Bunq-Client-Signature-Validation-Policy` header of the request to `IGNORE_ONLY_FOR_TESTING`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is now X-Bunq-Client-Signature
:)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True. Fixed it!
DESCRIPTION.md
Outdated
|
||
Here is how to encrypt a request: | ||
1. Generate a random [Initialization Vector](https://en.wikipedia.org/wiki/Initialization_vector) (IV) of 16 bytes. | ||
1. Generate a random [Advanced Encryption Standard](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) (AES) key of 32 bytes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is my bad, since I told you wrong, but lets make it 256 bits (32 bytes)
since in terms of encryption we should always talk in bits. (it is practically the same since 32bytes == 256bits, but makes more sense like this)
(Thats what AES-256
-CBC a few lines down comes from) :)
No description provided.