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.

Sign up for GitHub

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

Jump to bottom

Require api_key for GET /entries action #22

Open
karmakaze opened this issue Aug 17, 2018 · 0 comments
Open

Require api_key for GET /entries action #22

karmakaze opened this issue Aug 17, 2018 · 0 comments
Milestone
0.3.0 Some Advanc...

Comments

@karmakaze
Copy link
Owner

karmakaze commented Aug 17, 2018 •
edited
Loading

Actions:

  • POST /entries
  • GET /entries?filters...

I can see that the POST would be used by each application component.
The GET would be used by the front-end UI.

The simplest is to give distinct access keys for each action. Another good idea is to give each application component a distinct access key which can infer the source.

Related #35
@karmakaze karmakaze changed the title Require api_key for actions other than DELETE /entries Require api_key for POST and GET /entries actions Aug 18, 2018
@karmakaze karmakaze changed the title Require api_key for POST and GET /entries actions Require api_key for GET /entries action Aug 20, 2018
@karmakaze karmakaze mentioned this issue Aug 20, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.3.0 Some Advanced Features
Development

No branches or pull requests
1 participant
@karmakaze