This recipe was verified on WordPress 6 with the
openid-connect-generic 3.11.3 plugin and
the Telegram channel. WordPress has not been tested with other channels.What you need
- a Veriqa server at an address the site can reach; in production, public HTTPS with a valid certificate;
- a Telegram bot created with @BotFather;
- WordPress administrator rights.
Steps
1
Deploy the Veriqa server
In Docker, follow the self-hosted quickstart; without Docker,
install it as an OS service.
2
Enable Telegram
Set the bot token and username as described in the Telegram section
of channel setup.
3
Declare a client with a secret
The WordPress client is confidential, with a
client_secret and the redirect_uri
https://your-site/wp-admin/admin-ajax.php?action=openid-connect-authorize. Where to declare it:
step 4 of the self-hosted quickstart.4
Install and configure the plugin
The
openid-connect-generic plugin and its settings are covered in sections 1 and 2 of the
WordPress page.5
Drop scope from the code exchange
Without this step, sign-in fails at the code exchange. Use either an mu-plugin on the site or a
quirk on the Veriqa side — section 3.
How to check
Start a sign-in on the WordPress sign-in page, scan the QR code and confirm in Telegram. The plugin log showslogin-success, and WordPress has a new user.
The account is created without an email: Telegram does not provide one. If your site requires an
email, use the Email channel or ask for the address after the first sign-in — see
What you get.
Next steps
- Veriqa in a CMS — how WordPress differs from other engines;
- Testing the integration locally — if you try the setup on your own machine first;
- Preparing for production — before going live.