ska
ska copied to clipboard
barseghyanartur
Sign data using symmetric-key algorithm encryption. Validate signed data and identify possible validation errors. Uses sha-(1, 224, 256, 385 and 512)/hmac for signature encryption. Custom hash algorit...
Think about allowing ska data to be placed in the request headers instead of the request body
Consider the following payload: ```json { "company":{ "name":"Royal Lafleur", "website":"http://google.com" }, "user":{ "first_name":"Yinthe", "last_name":"van Dagsburg", "email":"[email protected]" }, "shipping_address":{ "street":"Ivyweg", "house_number":"8", "city":"Schore", "postal_code":"8374IE", "country":"NL" }, "billing_address":{ "street":"Femkeboulevard", "house_number":"7", "city":"Hallum", "postal_code":"5594TA", "country":"NL"...
``validate_provider_signed_request`` similar to ``validate_signed_request``.
Similar to #6, but should work with ``django-constance``.
In case if someone doesn't really want to use authentication backend, but just DRF permissions.
Metadata
Owner
Metadata
Sign data using symmetric-key algorithm encryption. Validate signed data and identify possible validation errors. Uses sha-(1, 224, 256, 385 and 512)/hmac for signature encryption. Custom hash algorit...