Skip to content
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

[FEAT] add client-receiver authentication #3

Open
edwinkys opened this issue Oct 31, 2024 · 0 comments · May be fixed by #16
Open

[FEAT] add client-receiver authentication #3

edwinkys opened this issue Oct 31, 2024 · 0 comments · May be fixed by #16
Assignees
Labels
enhancement New feature or request

Comments

@edwinkys
Copy link
Contributor

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.

@edwinkys edwinkys added the enhancement New feature or request label Oct 31, 2024
@edwinkys edwinkys self-assigned this Nov 6, 2024
@edwinkys edwinkys linked a pull request Nov 7, 2024 that will close this issue
5 tasks
@edwinkys edwinkys linked a pull request Nov 7, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant