By all means give it a try. Head to https://chutten.github.io/telemetry-dashboard/ and get into the Measurement Dashboard. There's a little login button at the top-right. It should redirect you to my auth0 for auth
user: user2@domain.com
pass: U$erdomain
If you successfully authenticate the login button should disappear and your access token will be at window.Telemetry.AuthorizationToken
Limitations:
Each navigation needs new auth
This includes refreshes and new tabs in addition to navigating between evo and dist
Auth0 is smart enough to auth you almost silently, so subsequent logins are just a matter of clicking the login button. No credentials. This may be low-friction enough for MVP, or may not.
No UI to let users know if they've auth'd or not.
The entire design is in need of review, so this isn't much surprise
Doesn't transmit auth to aggregates.tmo
aggregates.tmo actually has some CORS on it saying we can't send any but the most standard of headers. Authorization isn't a "most standard" so I had to comment it out.
No handling for token expiry
Tokens are configured to be valid for 2 hours, but I've not implemented any way of renewing it beforehand or handling a case where auth goes wrong.
User sessions are short enough and Auth0 authentication is seamless enough that this might be acceptable for MVP.
By all means give it a try. Head to https://chutten.github.io/telemetry-dashboard/ and get into the Measurement Dashboard. There's a little login button at the top-right. It should redirect you to my auth0 for auth
user: user2@domain.com pass: U$erdomain
If you successfully authenticate the login button should disappear and your access token will be at
window.Telemetry.AuthorizationToken
Limitations:
Authorization
isn't a "most standard" so I had to comment it out.