Cloud PortalUpdated November 1, 20262 min read
Directory and identity
One Administration hub for organizational directory and portal sign-in — SSO/SCIM for people, Agent One Active Directory follow for device inventory. Credentials stay separate.
Directory and identity
Open Administration → Directory & identity.
Customers often think of “our Active Directory” as one source. In Trustity Cloud Portal that story has two connectors:
| Purpose | Where you configure it | How it works |
|---|---|---|
| Portal sign-in | Directory & identity → Identity / SSO | Entra ID, Okta, or another IdP via SAML + optional SCIM. Password + MFA remains break-glass. |
| Device tree inventory | Devices & Tags / Managed devices (Device tree) | Domain-joined Agent One readers use LDAPS on your network and upload snapshots. |
The hub shows Identity as a link and shows a read-only inventory status for Active Directory follow. It does not copy LDAPS bind credentials into SSO, and SSO does not dial your domain controller.
Cloud AD (Entra ID)
- Open Identity / SSO from the hub.
- Follow the Entra checklist: Enterprise app (SAML), paste Trustity ACS values into Entra, save domain + App Federation Metadata URL (not
/saml2) in the portal (Save SSO registers Auth automatically — no Supabase access). - Enable the SSO toggle, then test Continue with SSO with a pilot user.
- Optionally create a SCIM token for user lifecycle.
On-prem AD
- People signing into the portal: sync AD into Entra (or Okta), then use SSO as above.
- Computers / OUs in the portal: keep using Device tree Active Directory with Agent One readers — see Follow Active Directory for devices and policy.