Docs menu
Updated 2026-10-23

Identity and login

The AgentHub app uses TokenDance Account for identity. Hub Server is a confidential OIDC relying party: it exchanges the authorization code on the server and maps the verified issuer and subject to a local AgentHub user.

Sign in

  1. Open the AgentHub app from the product website.
  2. Choose the TokenDance Account sign-in option in the app.
  3. Complete the methods offered by Account and return to AgentHub.
  4. Hub issues its own session and checks product permissions.

The product website provides documentation and application links. It does not start OIDC, receive authorization codes, store access or refresh tokens, or share a session with the app. The website’s old login and registration URLs now provide a link to the app. The retired TokenDance ID issuer is not an active sign-in option.

Account enrollment follows its invitation policy. Provider buttons appear only when Account has enabled and configured that provider; a provider name in a design document does not mean that it is available.

Sessions and sign-out

Account authentication and an AgentHub session are separate. Account tokens stay on Hub Server and are not model API keys. The current Web client keeps Hub’s own refresh token in tab-scoped browser storage, with a memory fallback; it is not an HttpOnly-cookie BFF.

Signing out in AgentHub revokes the Hub session. RP-initiated Account logout and Account back-channel logout are not implemented in this integration, so an Account-side sign-out or suspension must not be assumed to revoke every existing Hub session immediately.

Permissions

Hub owns access to conversations, projects, teams and product actions. Local execution additionally requires an authorized Edge target, workspace policy and any required approval. Signing in does not grant arbitrary filesystem or process access.

Feishu/Lark is a separate collaboration integration. Planned account mapping and event handling do not make Feishu an alternative identity authority.

Troubleshooting

  • If sign-in does not complete, retry from the app, not from a bookmarked callback URL.
  • If Account rejects enrollment, check the invitation and available sign-in methods.
  • If the app returns an authorization error, check the Hub session and permissions for that action.
  • Never send authorization codes, session tokens, provider responses or client secrets in an issue or screenshot.

See Security, Data and privacy and the public Account integration guide.

Edit this page on GitHub