g
g-authIdentity Center
g

Private identity control plane

Your access, in one place.

Review application access, security activity, and the identity evidence g-auth uses—protected by your browser’s non-exportable key.

Preparing this browser…

Identity overview

Good to see you.

● Proof-bound

Current identity

Session trustVerified
Connected applications—currently allowed
Browser keyNon-exportableWebCrypto P-256
Latest activity—security event

Assurance

Why g-auth trusts this session

Connected applications

Revoking access invalidates existing credentials and sessions immediately.

Recent authentication and access events.

Your sign-in credentials

Add a passkey or a FIDO2 security key to sign in directly to your existing account. Your other sign-in methods remain available.

Security keys need FIDO2 support, a PIN, and a touch. Enrollment continues securely on g-auth.

Removing a credential also ends sessions signed in with it.

Inspect and end logins across your applications.

Each row is one key-bound login. Reopened connections share that login. Active means access is valid, not that a browser is currently online. Ended logins are retained for 30 days after expiry.

Issue a one-use ticket bound to an agent’s private key. The ticket cannot authenticate by itself.

No applications currently allow agent enrollment for your account.

New authorization

Issue an agent ticket

g-auth stores only a hash of the ticket secret. The public key and permissions are fixed before enrollment.

Shown once

Transfer this ticket to the agent now

Anyone who sees it still needs the bound private key. It will disappear when you leave or refresh this page.

Authorized machines

Agents and pending tickets

Add users, invite them to enroll a passkey, and manage application access.

Add user

New users can manage their own credentials and sessions. Set their app access below; apps open to every authenticated user are available after sign-in.

Registered applications and their access policies.

Every application has a permanent ID and exact sign-in bindings. Registration enables g-auth integration; the application still needs to run its own verifier.

Register application

Sign-in providers
An administrator must grant each user access.
Agent enrollment (optional)

Saving changes invalidates this app’s existing credentials and enrollment tickets. Origin, audience, and ID cannot be reassigned. Callbacks must match a registered URL exactly.

Administration history

Recorded atomically with each change.