🚀 Feature: webfinger endpoint under .well-known #395

Closed
opened 2025-10-07 00:13:24 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @ryanmilvenan on GitHub.

Feature description

Add a webfinger endpoint to enable webfinger support

Pitch

This would make setting up an OIDC provider for Tailscale a breeze

Originally created by @ryanmilvenan on GitHub. ### Feature description Add a webfinger endpoint to enable webfinger support ### Pitch This would make setting up an OIDC provider for Tailscale a breeze
OVERLORD added the feature label 2025-10-07 00:13:24 +03:00
Author
Owner

@cdanis commented on GitHub:

https://webfinger.net/

@cdanis commented on GitHub: https://webfinger.net/
Author
Owner

@stonith404 commented on GitHub:

I don’t believe it makes sense to implement Webfinger directly into Pocket ID. As far as I know, the only client that specifically requires Webfinger is Tailscale. Moreover, this endpoint is primarily used during setup, and you can easily expose it using your reverse proxy for that purpose. For example, Authelia also doesn’t include Webfinger by default and instead recommends users expose the endpoint themselves.

@stonith404 commented on GitHub: I don’t believe it makes sense to implement Webfinger directly into Pocket ID. As far as I know, the only client that specifically requires Webfinger is Tailscale. Moreover, this endpoint is primarily used during setup, and you can easily expose it using your reverse proxy for that purpose. For example, Authelia also doesn’t include Webfinger by default and instead recommends users expose the endpoint themselves.
Author
Owner

@kmendell commented on GitHub:

@ryanmilvenan Are you referring to YubiKeys? or am i miss understanding?

@kmendell commented on GitHub: @ryanmilvenan Are you referring to YubiKeys? or am i miss understanding?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id#395