Browse the documentation
Haomai Technology AI Brain

Prepare SSO and embed Haomai Technology AI Brain in a business system

Give users access through their existing business application while preserving identity and data scope. Validate sign-in, role mapping and page embedding separately.

Technical guide · November 20263 min read

Define identity mapping

Identify the organization's identity system, authentication protocols supported by the product and user lifecycle. Link accounts with a stable identifier and use organization and role attributes to determine scope. A name or email address can change and should not be the sole basis for identifying someone.

Define specific rules for external collaborators, deactivated accounts of former employees and cross-department roles. After verifying first sign-in, test attribute updates, revocation, session invalidation and sign-out.

Build an integration checklist

AreaWhat to verify
AuthenticationSupported protocols, signature verification, validity periods and callback configuration
AccountsAccount creation, linking, deactivation and handling of duplicate identities
PermissionsMapping organizational attributes to product roles and data scope
SessionsExpiration, refresh, sign-out and behavior after revocation
EmbeddingAllowed origins, page policies and navigation behavior

Preserve authorization when embedding

Embedding a page in a portal must not cause all visitors to share a privileged identity. The embedded application still needs to determine the current user and their scope. Make it clear how to recover from errors and follow links to sources.

Support for iframes, redirect-based sign-in and other embedding methods depends on the product release and enterprise browser policy. Use this checklist to plan the work and the formal integration guide for protocol parameters, signature algorithms and configuration fields.

Validate before launch

  1. Test ordinary, restricted and deactivated identities separately in the test environment.
  2. Test callback origins, expired credentials, sign-out and role changes.
  3. After navigating between systems, check that the previous question's reporting period and permissions are not inherited incorrectly.
  4. Use the target browsers to verify page display, downloads, links back to cited sources and error messages.

Try “permissions,” “data source,” “manufacturing” or “API.”