-
Notifications
You must be signed in to change notification settings - Fork 605
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
refactor: deprecating cookie
and start sending token and expirations
#3573
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -21,13 +21,35 @@ message GithubLoginRequest { | |
} | ||
|
||
message GithubLoginResponse { | ||
// Deprecated | ||
// In future version, this cookie won't be sent. Now, old cookie is sent alongside the new expected | ||
// data (token, token_expires_at and refresh_token_expires_at). Frontend will be responsible of computing | ||
// its own cookie from the new data. | ||
// Remove after completing https://github.com/grafana/explore-profiles/issues/187 | ||
string cookie = 1; | ||
// base64 encoded encrypted token | ||
string token = 2; | ||
// Unix ms timestamp of when the token expires. | ||
int64 token_expires_at = 3; | ||
// Unix ms timestamp of when the refresh token expires. | ||
int64 refresh_token_expires_at = 4; | ||
} | ||
|
||
message GithubRefreshRequest {} | ||
|
||
message GithubRefreshResponse { | ||
// Deprecated | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same idea as the above comment. |
||
// In future version, this cookie won't be sent. Now, old cookie is sent alongside the new expected | ||
// data (token, token_expires_at and refresh_token_expires_at). Frontend will be responsible of computing | ||
// its own cookie from the new data. | ||
// Remove after completing https://github.com/grafana/explore-profiles/issues/187 | ||
string cookie = 1; | ||
// base64 encoded encrypted token | ||
string token = 2; | ||
// Unix ms timestamp of when the token expires. | ||
int64 token_expires_at = 3; | ||
// Unix ms timestamp of when the refresh token expires. | ||
int64 refresh_token_expires_at = 4; | ||
} | ||
|
||
message GetFileRequest { | ||
|
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's expand on why this is deprecated and possible link to some issues surrounding the deprecation decision. This includes the fact that for now
cookie
will still have the right value, but at some point in the future, we're going to release a version wherecookie
isn't used.This isn't an API that we advertise as supported, so the audience isn't the general public, but rather us down the road.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done