[Feature Request] Update Tailscale widget to use OAuth

[Gex2501]

Description

The Tailscale widget currently requires generating an API key, but keys with Tailscale have a maximum expiration of 90 days. Kinda annoying to have to generate a new key and update Homepage like that. Instead, can we update Homepage to use the Tailscale OAuth client's option? That seems like a better option...
https://login.tailscale.com/admin/settings/oauth

Other

No response

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

To implement Tailscale OAuth client's option for the Homepage widget, it would require changes to the Homepage codebase to support OAuth authentication. Currently, the widget configuration as provided in the context requires an API key. OAuth integration typically involves a more complex flow, including user redirection to the OAuth provider (Tailscale in this case), permission granting, and handling OAuth tokens.

This feature request would be a significant change and would need to be developed and tested by the Homepage development team. You can suggest this enhancement by creating a feature request on the Homepage GitHub repository. Make sure to provide a clear description of the feature, its benefits, and possibly reference the Tailscale OAuth documentation. If the community shows interest and the maintainers approve, it could be added to the project's roadmap.

For now, you will need to continue generating a new API key every 90 days as per Tailscale's policy or explore if there are any other methods to automate the key renewal process.

If you decide to create a feature request, follow the contribution guidelines provided in the context and check if there are any existing discussions or issues regarding OAuth integration for Tailscale on the Homepage repository.

This comment was generated by Glime.

[shamoon]

Yea the bot doesn’t quite seem context-aware ie that this is a FR.

wrt the FR itself, not sure how practical it is, it would require homepage handling the other end of oauth, which doesn’t exist at all at the moment

[Gex2501]

I don't know what's involved in using OAuth. I had just asked Tailscale support for a way to have a longer expiration time or never expire the api key but their reply was to use OAuth. Too bad their isn't some kind of script or something that can handle generating the OAuth and then just save whatever key is generated in Homepage...

[Lifeismana]

Adding support for Oauth clients should be quite easy since you can get an access token that replaces api keys in a single request:

curl -d "client_id=${OAUTH_CLIENT_ID}" -d "client_secret=${OAUTH_CLIENT_SECRET}" \
     "https://api.tailscale.com/api/v2/oauth/token"

And client id & secret don't expire
doc on this: https://tailscale.com/kb/1215/oauth-clients

[b1be]

tailscaleapikey.sh

#!/bin/bash
KEY=$(curl -s -d "client_id=#YOURID#" -d "client_secret=#YOURSECRET#" "https://api.tailscale.com/api/v2/oauth/token")
AUTH=$(echo $KEY | grep -o '"access_token":"[^"]*' | grep -o '[^"]*$')
sed -i "s/\btskey-api-[^ ]*/$AUTH/g" /opt/homepage/config/services.yaml

since oauth key validity is 3600 seconds (1 hour)

crontab -e
0 * * * * /home/#YOURUSER#/tailscaleapikey.sh

adjust to your configuration acordingly.
/opt/homepage/config/services.yaml , /home/#YOURUSER#/tailscaleapikey.sh , #YOURID# , #YOURSECRET#

[ghzgod]

THANK YOU!!