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

BUG - GET Profile endpoint requires authorization, should allow public access #416

Open
joneubank opened this issue Jun 28, 2024 · 0 comments
Assignees
Labels
authorization Issue is related to user auth or permissions. bug Something isn't working good first issue Good for newcomers

Comments

@joneubank
Copy link
Contributor

Description

The GET profile endpoint is intended to inform the client which object storage backend to expect to interact with. This will be needed for both controlled and open access files, which means that this endpoint should not have any auth restrictions since open files can be downloaded by the public.

Currently this endpoint is only available to authenticated users that provide a valid token in the Authorization header.

Expected Behaviour

All requests to this endpoint should return the profile without authorization restrictions.

Actual Behaviour

All requests without an authorization header with valid token are rejected.

Steps to Reproduce

On any running Score server, send a request like:

curl -X GET "https://score.example.org/profile" -H "accept: */*"

Your Environment

Replicated in local running score instance as of commit e5505bc - release version 5.10.1.

@joneubank joneubank added bug Something isn't working good first issue Good for newcomers authorization Issue is related to user auth or permissions. labels Jun 28, 2024
@joneubank joneubank self-assigned this Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
authorization Issue is related to user auth or permissions. bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant