Configure identity and authentication
HP Insights signs in two kinds of people: print users, who release and manage their print jobs, and administrators, who use the web console. Set up print user sign-in first, because Secure Print and Secure Print Direct depend on it. Administrator single sign-on and SCIM provisioning are optional and can be added later.
If you're deploying Fleet Manager or HP Insights only, you don't need a print user authentication provider. You still need administrator access to the web console, so go straight to step 3.
Before you begin
- You've activated HP Insights. See Activate HP Insights.
- You know which identity provider your organization uses, and whether it supports OpenID Connect (OIDC) or SAML 2.0.
- For OIDC, you have the Well-Known Endpoint, Client ID and Client Secret. For SAML, you have the Entity ID and Metadata URL.
- You've decided how print users and administrators will sign in. See Choose how administrators and print users sign in.
- For the concepts behind these steps, see How users are identified.
Set up sign-in
Set up the print user authentication provider
Choose OIDC or SAML 2.0 and configure it under Account Settings > Settings > User Authentication Providers. Your environment has one provider, and every print user and workflow uses it.
- User Authentication Providers: compare the options and what each supports.
- Configure OpenID Connect
- Configure SAML 2.0, or Configure SAML with Microsoft Entra ID if you use Entra ID.
Test print user sign-in
The Test button alone isn't enough. Sign a real user in as well, in a private browser window, so that consent and redirect problems show up now rather than at rollout. See Verifying the configuration.
Decide how administrators sign in
Administrators can sign in to the web console with internal accounts, or with single sign-on through your identity provider. With Admin SSO and SCIM, administrator accounts, groups and roles are managed in your identity provider and kept in sync automatically.
- Configure SSO for system user login: compare the options.
- Configure SSO with SCIM for system users (Admin SSO)
You can complete setup with internal administrator accounts and add Admin SSO later.
Provision users and groups with SCIM (optional)
SCIM creates, updates and removes users and groups from your identity provider, so you don't maintain them by hand. See SCIM user and group provisioning, then follow the guide for Microsoft Entra ID, Okta or Ping Identity.
Give other administrators access
Add the other people who will run HP Insights and give each one a role. How you do this depends on step 3:
- Without Admin SSO: add them in Users > System Users. See Give other administrators access.
- With Admin SSO: System Users is read-only. Roles come from Users > Group Mapping, based on each administrator's identity provider group.
To choose roles, see Licensing, roles and administrator access.
Result
- Print users can sign in through your identity provider, and you've tested it with a real user.
- Administrators can sign in to the web console, and each has the role they need.