We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As discussed in #2, we need a way to authenticate clients to Shaarli's API.
I'm in favor of using JWT:
@virtualtam has proposed to used an authentication process
When emitting several requests over an HTTP service that requires authentication, one usually: opens an HTTP session with a first request carrying the credentials, reuses this session to send further requests
When emitting several requests over an HTTP service that requires authentication, one usually:
Another possibility is OAuth in client_credentials mode. IMHO it's a bit too complex but it's not that hard:
client_credentials
refresh_token
EDIT: actually OAuth without a database is a bad idea, because we need to store clients, authorization code and tokens, at least.
The text was updated successfully, but these errors were encountered:
More on JWT:
Actively maintained PHP libs:
Sorry, something went wrong.
No branches or pull requests
As discussed in #2, we need a way to authenticate clients to Shaarli's API.
I'm in favor of using JWT:
@virtualtam has proposed to used an authentication process
Another possibility is OAuth in
client_credentials
mode. IMHO it's a bit too complex but it's not that hard:refresh_token
endpointEDIT: actually OAuth without a database is a bad idea, because we need to store clients, authorization code and tokens, at least.
The text was updated successfully, but these errors were encountered: