-
Notifications
You must be signed in to change notification settings - Fork 159
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
feat: add authentication headers when proxying pipeline websocket requests #1457
Closed
+23
−2
Closed
Changes from 9 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
7be8988
feat: Issue an auth token for the pipeline service websocket
rapsealk 47d12b6
docs: Add news fragment
rapsealk 830adff
docs: Rename the news fragment with the PR number
rapsealk 2d222f3
docs: Update news fragment
rapsealk 79d532a
Merge branch 'main' into feature/pipeline-auth-token-ws
rapsealk 308f859
fix: Get api session for the pipeline service
rapsealk 8b685d0
fix: Use `datetime.datetime.astimezone()`
rapsealk f02aad1
fix: Update token expiry date to 1 day last
rapsealk 0e998f7
fix: Update webserver config
rapsealk 9fcb056
Merge branch 'main' into feature/pipeline-auth-token-ws
kyujin-cho 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
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 |
---|---|---|
@@ -0,0 +1 @@ | ||
Add `X-BackendAI-SessionID` and `X-BackendAI-SSO` headers to the pipeline websocket proxy handler. |
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
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
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.
If I am guessing correctly, this
jwt
directive is for the traffics from FastTrack. FastTrack is a private project and thus only limited number of users who operate Backend.AI webserver will be required to fill out this field. When taking account into this situation I don't think this wholepipeline
configuration body should be a required config values. Please refactor the validator to either mark thepipeline
configuration as an Optional value or at lease leavejwt
as nullable and dynamically check its existence when the request actually comes from the FastTrack side.