leviathonbeast/ionscale
1
0
Fork 0
mirror of https://github.com/jsiebens/ionscale.git synced 2026-03-31 15:07:49 +01:00
Code Issues Packages Projects Releases Wiki Activity

update docs

Browse Source
This commit is contained in:
Johan Siebens
2025-04-29 07:24:54 +02:00
parent 442d794189
commit d5a5a924ca
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mkdocs/docs/getting-started/tailnet.md
+3 -3
View File
@@ -84,6 +84,9 @@ Example policy.json file:
There are two main methods to connect devices to your tailnet: There are two main methods to connect devices to your tailnet:
!!! tip
For detailed instructions on configuring various Tailscale clients to use ionscale as a control server, refer to the [Tailscale Knowledge Base](https://tailscale.com/kb/1507/custom-control-server).
### Interactive login ### Interactive login
When you have an OIDC provider configured, users can connect to their tailnet through an interactive web authentication flow: When you have an OIDC provider configured, users can connect to their tailnet through an interactive web authentication flow:
@@ -123,9 +126,6 @@ To connect a device using an auth key:
tailscale up --login-server=https://ionscale.example.com --auth-key=... tailscale up --login-server=https://ionscale.example.com --auth-key=...
``` ```
!!! note
Auth keys in ionscale are single-use by default. Once a key has been used to authenticate a device, it cannot be used again.
## Network access and security policies ## Network access and security policies
By default, tailnets are created with an open policy that allows all connections between devices. For production environments, you'll want to configure: By default, tailnets are created with an open policy that allows all connections between devices. For production environments, you'll want to configure: