Login and certificate issues

#Browser certificate warning

New installs use a self-signed certificate until you install your own, so a warning is expected at first.

• Confirm you're opening FileAgent with a name covered by the certificate.
• Install a trusted certificate under Settings → System Configuration → HTTPS / TLS Certificate (see Certificates).
• After replacing a certificate, restart the web service if it isn't served immediately.

#Can't sign in

• Confirm the account is active and the password is correct; watch for accidental whitespace.
• If the account is locked after failed attempts, an administrator can unlock it under User Management.
• If you've enabled directory or SSO sign-in, use the correct method shown on the sign-in screen — and remember administrators retain a local recovery sign-in.

#SSO sign-in fails

• Confirm the active license includes SSO (Business Premium or Enterprise).
• Use a SAML 2.0 application in the identity provider, not OIDC/OpenID Connect.
• Make sure the ACS URL, Entity ID, and metadata URL use the same HTTPS base URL administrators use in the browser.
• Check the IdP signing certificate is current and the host clock is synchronized (SAML validity windows are time-sensitive).
• If users authenticate but can't enter FileAgent, review auto-provisioning, allowed domains, group claims, and role mappings.

See Single Sign-On (SSO) for full setup.