Skip to content

Sign-in for your websites and apps

Bring your websites and apps together in one project and give customers an easy way to sign in with vixar.id.

Email and passwordGoogleYandex IDVK IDPasskey

What you can do

  • Your customers in one project

    Connect multiple websites and apps to one project with a shared user base. Customer management in the dashboard is planned.

  • Connect through OAuth 2.0 and OpenID Connect

    Create a project and app in your account, add your callback URL and get your client ID. A server app also gets a client secret; browser apps use PKCE without a secret.

How users can sign in

Users choose how to sign in to vixar.id. One account works across connected services.

Email and passwordGoogleYandex IDVK IDPasskey

How to add sign-in

  1. Create a project

    Create a project for websites and apps with a shared user base.

  2. Add an app

    Choose the app type and the address users return to after signing in.

  3. Connect vixar.id

    Use your client ID with OAuth 2.0 or OpenID Connect. See the documentation for an integration example.

For websites and apps

  • Server app

    Use your client ID and keep your client secret on the server.

  • Browser app

    Choose a public client and use PKCE without a client secret.

Before you connect

Where does the user return after sign-in?
To the callback URL configured for your app. It must exactly match the URL in the request.
Where should I store the client secret?
Keep it on your server. Do not put it in browser code or a public repository.
What should I use for a browser app?
Choose the public app type and use PKCE. It does not need a client secret.

Connect your websites and apps

Create a project and add an app, or start with the documentation.