Skip to main content
Your team works in GitLab, Grafana, Nextcloud or another business system, and you want employees to sign in to it through Veriqa instead of a password. The Veriqa server runs inside your network.
Business systems were verified with the Email channel. On Telegram, the systems react differently to a missing address — see The email requirement.

​
What you need

  • a machine inside your network for the Veriqa server;
  • a mailbox for the Email channel, or a messenger bot;
  • administrator rights in the business system.

​
Steps

1

Deploy the Veriqa server

Without Docker, install it as an OS service; in Docker, follow the self-hosted quickstart.
2

Enable a channel

For the verified setup, use the Email channel.
3

Declare a client for the system

Add the system and its redirect_uri to Veriqa:OpenIddict:Clients — step 4 of the self-hosted quickstart.
4

Configure the system

Follow the section for your system on the Veriqa in business systems page: GitLab, Grafana, Nextcloud and others. Each one names the barrier and how to clear it.
5

Enable a quirk if the system sends extra parameters

If the system sends parameters that Veriqa rejects, enable a quirk for its client — see Client compatibility.

​
How to check

Sign in to the system through Veriqa and confirm the sign-in. The employee’s account should be created automatically; on Discourse, only the sign-in of an existing user was verified. If you set up the system on your own machine first, the issuer sits in a private network, and the system may refuse to call it. The switch for each system is listed under Local testing.

​
Next steps