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

API: Add support for /authenticate request #3

Closed
rtamalin opened this issue May 31, 2024 · 1 comment
Closed

API: Add support for /authenticate request #3

rtamalin opened this issue May 31, 2024 · 1 comment
Labels
API Requests enhancement New feature or request

Comments

@rtamalin
Copy link
Collaborator

The headers of the /authenticate request must include the following items:

  • client id
  • SHA256 of the existing authentication token

The payload of the /authenticate request contains the following items:

  • SHA256 of the client instance id
    • optional, only required if a client is requesting a new token because the existing one has expired or is no longer valid
@rtamalin
Copy link
Collaborator Author

This underlying work for this was completed as part of #38.

The authentication approach was simplified to just requesting an updated client credentials set that includes a freshly generated auth token. The authenticate request requires a payload containing the client's id, and hash digest of it's instance id. These will be used by the server to validate that the client is registered with the server, and that the provided hash digest matches that of the client instance it provided when the client registered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Requests enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant