🔒️(project) move copilot token request to backend #7
Conversation
This file contains hidden or 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
The Copilot Endpoint URL is not a secret per se. However, we anticipate that in the future, we will use a Copilot that requires passing a secret in the Endpoint URL request's header. Thus, we no longer pass the Copilot Endpoint URL to the client JavaScript to avoid exposing this secret to Moodle users and make the request on the backend side instead.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
The Copilot Endpoint URL is not a secret per se.
However, we anticipate using a Copilot that requires passing a secret in the Endpoint URL request's header in the future.
Proposal
To avoid exposing the Copilot Endpoint URL secret to Moodle users, we perform the conversation token request on the backend side.