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

Create $public client #437

Open
eduardoboucas opened this issue Jun 19, 2018 · 0 comments
Open

Create $public client #437

eduardoboucas opened this issue Jun 19, 2018 · 0 comments

Comments

@eduardoboucas
Copy link
Contributor

Currently, it's possible to make a collection or custom endpoint open to the public (i.e. requests without a bearer token) using the settings.authenticate property.

Whilst this works, it's an all or nothing kind of thing. It's not possible to take full advantage of ACL features like limiting access to a subset of the collection fields or specify a permissions filter. We could achieve this by introducing a special client (e.g. $public) that would represent unauthenticated requests.

Assigning public permissions to a resource would work in the same way as granting permissions to any other client does – i.e. a POST request to /api/clients/$public/resources.

We can easily keep support for settings.authenticate for backward compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants