Denton Gentry

> When the session fails due to token expiration, there needs to be a large popup prompting the user to reauthenticate. You may not believe it, but there is one....

Since we're piling on with a plethora of options, the functionality will also appear in a macOS TestFlight build. You can join the TestFlight at https://testflight.apple.com/join/7ExrFq00

The backend peerapi support for this feature will appear in 1.26.

I understand and do intend to. We are finishing the 1.56 client release this week. We would want something like this to go in at the start of a new...

Requiring import was the fix for https://github.com/tailscale/terraform-provider-tailscale/issues/182, whatever we do here needs to ensure it doesn't re-introduce the same problem.

There are several Hashicorp vault providers which can handle tailscale key state: https://github.com/bloominlabs/vault-plugin-secrets-tailscale https://github.com/davidsbond/vault-plugin-tailscale The most recent updates in https://github.com/tailscale/tailscale/issues/3243 describe the intended solution: an [OAuth 2.0 Client Credential flow](https://www.rfc-editor.org/rfc/rfc6749#section-4.4)...

> @DentonGentry the existence of other solution doesn't negate the problems with this one. If not pulling secrets from Hashicorp vault or similar solutions, then what would you propose?

The 1.40 release currently in the App Center was released in June, six months ago at the time of this writing. We wanted the [updated web interface](https://tailscale.com/kb/1325/device-web-interface) to be in...

We did not finish the 1.56.1 release prior to the holidays, we're posted 1.56.1 on tailscale-qpkg. > Even the qpkg on github is outdated by few months. Weeks, not months.

We have one issue in the web client in 1.56.1 which we want to fix before submitting to the App Center. We're now expecting to submit 1.58.