You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: mkdocs/docs/getting-started/tailnet.md
+15-28Lines changed: 15 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,52 +82,39 @@ Example policy.json file:
82
82
83
83
## Connecting devices to your tailnet
84
84
85
-
How devices connect to your tailnet depends on your authentication configuration:
85
+
There are two main methods to connect devices to your tailnet:
86
86
87
-
### Using OIDC authentication
87
+
### Interactive login
88
88
89
-
If OIDC is configured, users with access (based on the IAM policy) connect via web authentication:
89
+
When you have an OIDC provider configured, users can connect to their tailnet through an interactive web authentication flow:
90
90
91
91
```bash
92
92
tailscale up --login-server=https://ionscale.example.com
93
93
```
94
94
95
-
This opens a browser window where users authenticate with the OIDC provider. After successful authentication, if the user has access based on the tailnet's IAM policy, the device will be connected.
95
+
This opens a browser window where the user authenticates with the OIDC provider. After successful authentication, if the user has access based on the tailnet's IAM policy, the device will be connected to the tailnet.
96
96
97
-
### Using auth keys
98
-
99
-
Auth keys allow devices to join a tailnet without interactive authentication. This is useful for automated deployments, servers, or environments where browser-based authentication isn't practical.
97
+
!!! note
98
+
Interactive login requires an OIDC provider to be configured on your ionscale instance.
100
99
101
-
There are two main scenarios for creating auth keys:
100
+
### Using pre-authentication keys
102
101
103
-
#### Without OIDC configured
102
+
Pre-authentication keys (auth keys) allow devices to join a tailnet without interactive authentication. This is useful for automated deployments, servers, or environments where browser-based authentication isn't practical.
104
103
105
-
When OIDC is not configured, a system administrator must create auth keys with appropriate tags:
In environments with OIDC, users with access to a tailnet can create auth keys for that tailnet. Without OIDC, only system administrators can create keys.
0 commit comments