Veriqa.Core.ChannelAdapter.Telegram
0.7.3
Prefix Reserved
dotnet add package Veriqa.Core.ChannelAdapter.Telegram --version 0.7.3
NuGet\Install-Package Veriqa.Core.ChannelAdapter.Telegram -Version 0.7.3
<PackageReference Include="Veriqa.Core.ChannelAdapter.Telegram" Version="0.7.3" />
<PackageVersion Include="Veriqa.Core.ChannelAdapter.Telegram" Version="0.7.3" />
<PackageReference Include="Veriqa.Core.ChannelAdapter.Telegram" />
paket add Veriqa.Core.ChannelAdapter.Telegram --version 0.7.3
#r "nuget: Veriqa.Core.ChannelAdapter.Telegram, 0.7.3"
#:package Veriqa.Core.ChannelAdapter.Telegram@0.7.3
#addin nuget:?package=Veriqa.Core.ChannelAdapter.Telegram&version=0.7.3
#tool nuget:?package=Veriqa.Core.ChannelAdapter.Telegram&version=0.7.3
Veriqa.Core.ChannelAdapter.Telegram
Telegram login and authentication by QR code for your website or app.
- Your users scan a QR code on the sign-in page (on a phone, they tap a button) and confirm the sign-in with one tap in Telegram: no password, no SMS code and no sign-up form.
- Your application receives standard OpenID Connect tokens with the user's name, language and photo and, with their consent, their phone number.
- Your users can sign in this way on a computer, a TV, a kiosk or any other device that can show a QR code.

This package is the Telegram channel of Veriqa, an open-source project for passwordless authentication through popular messaging apps and email, over standard OpenID Connect. Setup guide: Telegram channel.
Telegram also has a sign-in of its own over OpenID Connect. With Veriqa, Telegram is one of several channels behind your own issuer, and the same setup also covers action confirmations and step-up: see How Veriqa differs.
Gallery: sign-in and confirmation in Telegram. Use cases: passwordless sign-in, second factor and step-up, all use cases.
About this package
The adapter turns the user's confirmation in your Telegram bot into the identity the core issues tokens for. It is one channel out of several: a deployment installs the channels it actually uses, and only the Telegram SDK travels with this one.
Install
dotnet add package Veriqa.Core.ChannelAdapter.Telegram
The channel contour (Veriqa.Core.ChannelAdapter) arrives with this package — it is not installed
separately.
Wiring
authServer.AddChannelAdapters(adapters => adapters.AddTelegram());
The adapter activates only when its configuration section Veriqa:Channels:Telegram is enabled
("Enabled": true); otherwise only its options and their validator are registered.
License
Mozilla Public License 2.0 — see the LICENSE file in the repository root; the package carries
the MPL-2.0 license expression in its metadata.
Veriqa™ — © Dmitrii Erusov. Sources and mirrors: https://veriqa.app · devs@veriqa.app
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Microsoft.Extensions.Http.Resilience (>= 10.4.0)
- Telegram.Bot (>= 22.9.5.3)
- Veriqa.Core.ChannelAdapter (= 0.7.3)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Veriqa.Core.ChannelAdapter.Telegram:
| Package | Downloads |
|---|---|
|
Veriqa.Core.BaseChannels
Telegram, WhatsApp and Email login and authentication in one package: a Veriqa metapackage pulling the channel contour together with the Telegram, WhatsApp and Email channels. Other channels ship as separate packages. |
GitHub repositories
This package is not used by any popular GitHub repositories.