Add OneProfileID
to your own site.
We’re planning support for other developers through OpenID Connect. Your app would use OneProfileID to identify the person signing in, then apply its own roles and permissions.
Developer access is planned. There is no public SDK or authentication service yet.
Your application
A person chooses to sign in with OneProfileID.
OneProfileID
They authenticate and review the information your app requests.
Back to your app
Your app verifies their identity and applies its own access rules.
Planned foundation: OpenID Connect ↗ for authentication. Scoped access for profile data. Your app’s data stays under your app’s control.
A familiar identity,
throughout your app.
These are the actual reusable OneProfileID components. Compare light and dark, try the buttons, and see how profile sync can appear in your settings.
Preview only. These controls do not sign you in.
How these components are shared
Buttons, marks, badges, and account controls come from one UI module. Light and dark colors come from the global Flygon style catalog. Change the shared source, rebuild the consumers, and every use gets the same update.
<opid-sign-in mode="auto" variant="solid"></opid-sign-in>
<opid-badge mode="auto"></opid-badge>
<opid-badge mode="auto" kind="synced"></opid-badge>
<opid-badge mode="auto" kind="backed"></opid-badge>
<opid-account name="Jamie Morgan" email="jamie@example.com"></opid-account>The component module must be loaded once. It provides the interface and interaction events; connecting those events to the future authentication service is a separate integration.