🚀 Feature: Enable usage as authentication back end

[levino]

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]

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.

[gedw99]

Hey @levino and @stonith404

pocketbase/pocketbase#6346 bring this up too as others are also looking to integrate Pocket-id with their Pocketbase apps.

For example https://github.com/henrygd/beszel uses Pocktbase, and has OIDC support, which is @henrygd project.

I am currently working on NATS AUTH Callout integration, to allow NATS Jetstream authentication and authorisation to be used off this. This allows Servers and Edge Servers to send and receive messages in order to built larger deployments of Beszel and Pocketbase systems. It uses a simple CRDT table structure inside the SQLITE DB to allow the multimastser ( offline / online ) replication as par CAP Theorem.

I currently use this approach to allow the Pocketbase Sqlite Db to be replicated across Cloud Servers, Edge Servers, and Browser Service Workers. It's just taking the changes and replicating, using the Users own Credentials. NATS AUTH call out works with OIDC by using the NATS NSC security system built into NATS Jetstream.