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

API Request: Finalize client side registration and report authentication #34

Closed
rtamalin opened this issue Jul 16, 2024 · 1 comment
Closed

API Request: Finalize client side registration and report authentication #34

rtamalin opened this issue Jul 16, 2024 · 1 comment
Assignees
@rtamalin
Labels
API Requests enhancement New feature or request

Comments

@rtamalin
Copy link
Collaborator

rtamalin commented Jul 16, 2024 •
edited
Loading

The /register REST API request obtains an auth token which needs to be included in the /report REST API request's headers as an Authorization header using the Bearer schema.

Additionally if a /report REST API request fails with a HTTP 401 Unauthorized this should:

  • clear the existing auth token to indicate that a new auth token needs to be collected
  • trigger an attempt to re-authenticate using the /authenticate REST API request.

Add support the /authenticate REST API request.

This work will be interdependent with that of the SUSE/telemetry-server#35 issue.
@rtamalin rtamalin added enhancement New feature or request API Requests labels Jul 16, 2024
@rtamalin rtamalin self-assigned this Jul 16, 2024
rtamalin added a commit that referenced this issue Jul 16, 2024
@rtamalin
Switch to using a JWT as the auth token
f5f10ce 
As part of the first phase of finalising the authentication method
we need to update the client side to send an Authorization header
using the Bearer schema that includes the auth token obtained from
the telemetry server via a previous /register request.

Remove redundant TokenSha256code.

Relates: #34
@rtamalin rtamalin mentioned this issue Jul 16, 2024
Merged
@rtamalin
Copy link
Collaborator Author

#38 and SUSE/telemetry-server#39 complete this work.

Telemetry report submissions must include:

  • an Authorization header in the Bearer schema specifying the auth token
  • an X-Telemetry-Client-Id specifying the client's id

The server will reject the request with HTTP 401 Unauthorized if the supplied auth token is not valid, or the client is not registered with the server, or the auth token doesn't match what the server has recorded for the client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rtamalin rtamalin

Labels
API Requests enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rtamalin