Sign-in and access
Every Netos environment sits behind your Netos zone, for example https://uks001.app.netos.io. The zone signs people
in, then opens NetBox as them with the groups they hold for that environment. This section is for the administrator
who sets that up.
What you need
- Your zone name from Netos, for example
uks001. - A list of the people or groups who should use each environment, and what each may do: for example read on production, edit on lab.
- To use your company sign-in: an administrator of your Okta or Microsoft Entra ID, and the email domains your people sign in with.
How sign-in works
sequenceDiagram
actor U as User
participant G as Netos zone
participant I as Netos ID or your sign-in
participant N as NetBox
U->>G: Open the Netos link, enter work email
G->>U: Continue with Netos ID, or with your company sign-in
U->>I: Sign in and second factor
I->>G: Identity and groups
G->>G: Map groups to NetBox groups for this environment
G->>N: Open NetBox as the user
- The user opens a Netos link and enters their work email.
- The zone looks at the email domain. A domain linked to your company sign-in goes there; any other email goes to Netos ID.
- The user signs in. Your sign-in, or Netos ID, applies its own password and second-factor rules.
- The zone maps the user's groups to NetBox groups for the environment they opened, and opens NetBox. NetBox creates the user on their first sign-in.
Each email domain is linked to one sign-in on a zone. Once your domain is linked to your company sign-in, people with that domain sign in to that zone only through it.
Choose a sign-in
| Sign-in | Use it when | Set up by |
|---|---|---|
| Netos ID (default) | You have no company sign-in to connect, or for partners and guests | Netos invites each person |
| Okta | Your people sign in with Okta | Your Okta administrator, with Netos |
| Microsoft Entra ID | Your people sign in with Microsoft 365 | Your Entra administrator, with Netos |
Netos ID
Netos ID is the sign-in Netos provides. Anyone whose email domain is not linked to a company sign-in on your zone uses it.
- Invitation only. There is no self sign-up. Netos invites each person and assigns them to your zone. Send Netos the name and work email of each person, and the access they should get.
- Signing in: the user enters their email, selects Continue with Netos ID, enters their password, then the code Netos ID sends to their email.
- Groups are kept by Netos. To change what someone can do, ask Netos.
- Removing access: ask Netos to remove the person. Their sessions end at the next check.
Multi-factor authentication
Netos treats a sign-in as multi-factor when your sign-in reports it. An environment can require it; production environments normally do. A user who signs in without a second factor is refused on an environment that requires one.
Sessions
- A browser session ends after a period of inactivity, and after a maximum length, both set for your zone.
- While a session is open, the zone checks the user with their sign-in again at a fixed interval. If your company disables the account or removes it from its Netos groups, the session ends at the next check.
- Group changes apply the next time the user signs in.
Troubleshooting
| What the user sees | Likely cause | Fix |
|---|---|---|
| Sent to Netos ID instead of your company sign-in | The email domain is not linked to your sign-in on this zone | Send Netos the domain |
| "Access denied" after sign-in | The user is in no group linked to this environment | Add them to a linked group, or ask Netos to link the group. See Groups and permissions |
| "Sign in failed" | Netos could not complete the sign-in with the provider | Send Netos support the reference ID on the page and the time |
| No Netos ID invitation | The person has not been invited yet | Ask Netos to invite them |