Skip to content
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

SignedUrls don't work for privateUrlUsers #10093

Closed
qqmyers opened this issue Nov 3, 2023 · 0 comments · Fixed by #10098
Closed

SignedUrls don't work for privateUrlUsers #10093

qqmyers opened this issue Nov 3, 2023 · 0 comments · Fixed by #10098
Labels
Type: Bug a defect
Milestone

Comments

@qqmyers
Copy link
Member

qqmyers commented Nov 3, 2023

What steps does it take to reproduce the issue?
The way privateUrlUser credentials are converted into an ApiToken in the Files API class doesn't provide a username for use in generating signedUrls (and username is required). This breaks generating signedUrls for use with externalTools/Previewers configured for signedUrls when accessed by a PrivateUrlUser.

Which version of Dataverse are you using?
5.14 - develop

PR to follow.

@qqmyers qqmyers added the Type: Bug a defect label Nov 3, 2023
pdurbin added a commit to QualitativeDataRepository/dataverse that referenced this issue Nov 21, 2023
pdurbin added a commit to QualitativeDataRepository/dataverse that referenced this issue Nov 21, 2023
pdurbin added a commit to QualitativeDataRepository/dataverse that referenced this issue Nov 21, 2023
pdurbin added a commit to QualitativeDataRepository/dataverse that referenced this issue Nov 21, 2023
pdurbin added a commit to QualitativeDataRepository/dataverse that referenced this issue Nov 21, 2023
@pdurbin pdurbin added this to the 6.1 milestone Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug a defect
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants