mirror of
https://github.com/pocket-id/pocket-id.git
synced 2025-12-09 09:13:15 +03:00
🚀 Feature: Enable usage as authentication back end #430
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @levino on GitHub.
Feature description
This is rather a question than a feature request or bug report. Please see #87 in order to reduce such abusive issues. Sorry about this one.
I am wondering if it was possible to use pocket id as an authentication back end (without an additional one). Currently I am using pocketbase for simple protection of resources and the respective user management. I could add pocket id as a OIDC provider in pocketbase. But this seems quite awkward / cumbersome to me. Is it possible to get simple access tokens directly from pocket id? If they contained the groups of the user, that would even be better because often I am managing a couple of apps for the same set of users and then I group them by app.
Pitch
Maybe just a matter of missing documentation. See #88.
@stonith404 commented on GitHub:
This isn’t possible, and I don’t plan to add it to Pocket ID. The goal of the project is to focus solely on being an OIDC provider. For more complex use cases, there are better options available, like Keycloak.
That said, it shouldn’t be too difficult to create your own solution. You could build a simple backend to issue access tokens and authenticate users with Pocket ID, or use something like Pocketbase, as you mentioned.