You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to add an authentication layer on top of the receiver server so that the client will need to authenticate before triggering a method like get approval. This will improve the security of the receiver server ensuring that only an authenticated client can perform certain actions.
Potential Solution
I'm thinking of using a simple secret key that we can setup in the server-side using an environment variable. This key will be checked by a middleware function for every request ensuring the authenticity of the request.
The text was updated successfully, but these errors were encountered:
Feature Description
We want to add an authentication layer on top of the receiver server so that the client will need to authenticate before triggering a method like get approval. This will improve the security of the receiver server ensuring that only an authenticated client can perform certain actions.
Potential Solution
I'm thinking of using a simple secret key that we can setup in the server-side using an environment variable. This key will be checked by a middleware function for every request ensuring the authenticity of the request.
The text was updated successfully, but these errors were encountered: