Scorm XBlock handle to serve SCORM content from a private S3 bucket #5
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.
Create the scorm_view function to serve SCORM content from a private S3 bucket using pre-signed URLs
Previously, the scorm_view function in the XBlock handler accessed files directly from the S3 bucket without any authentication, which posed a security risk. To address this issue, we updated the function to use the get_presigned_url function, which generates a pre-signed URL for accessing the file in the private S3 bucket. We then used this pre-signed URL to retrieve the file content and return it with the appropriate content type.
This update ensures that SCORM content is served securely from a private S3 bucket using pre-signed URLs, improving the overall security of the XBlock handler.