> ## Documentation Index
> Fetch the complete documentation index at: https://veriqa.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 0.6.10 — sign-in and confirmation as one process

> What Veriqa gained in stage 0.6.10: the same pages for sign-in and confirmation, a color for a channel's button, a confirmation mode per channel and a sample with Google, Apple and Huawei sign-in.

> [!NOTE]
>
> A development stage from October 18 to 22, 2026. There is no 0.6.10 package: these changes shipped in
> [0.7.0](https://veriqa.app/docs/releases/0.7.md).

## Sign-in and confirmation

A sign-in and a server-to-server confirmation now work the same way for the user: the same pages,
deadlines, status lines and receipts. What differs is the words that name the action and the rare case
with a technical reason, like the email answer below.

* A confirmation gets the same "Yes"/"No" question page as a sign-in and a cancel button of its own;
  canceling gives your application the outcome `declined`.
* The channel button says what the page is for: `Sign in with {0}` or `Confirm in {0}`. The
  instruction does the same and, on a tab, names the selected channel.
* The confirmation email has its own wording: the subject `Confirmation for {app}`, the heading
  `Confirmation required` and the button `Continue to confirmation`. The sign-in email is unchanged.
* Where only the browser that opened the email link can answer, the confirmation window stays in
  place and shows a line saying so, the countdown and the cancel button.

## The sign-in page

* **A color for one channel's button** — see
  [Channel button colors](https://veriqa.app/docs/guides/customization.md#channel-button-colors). The same color tints the
  channel's icons on tabs, panels and the instruction line.
* **A confirmation mode per channel:** the `ModeByChannel` map in the deployment settings and
  `LoginConfirmationModeByChannel` at the tenant and application levels — see [Veriqa:LoginConfirmation](https://veriqa.app/docs/reference/configuration.md#veriqaloginconfirmation).
* **Your own instruction for a page without the QR code or without the button:** the
  `instruction_without_qr` and `instruction_without_button` fields of a `ui_config` record.
* The name of a built-in channel is translated with the `<Name> | channel` string and reads the same on
  the button, the tab and the instruction.
* The hop page a scan opens gets a cancel button, and the question on the "Yes"/"No" page comes from
  the `confirmation-prompt` message kind.
* The texts of the page that completes a sign-in through `form_post` join the `AuthPage.Texts` list.

## Security

Transitive dependencies with known vulnerabilities are updated: `System.Security.Cryptography.Pkcs`
to 10.0.13 and `MessagePack` to 2.5.303.

## Samples

A new sample, `samples/dotnet/custom-channel-id-providers`: sign-in through Google, Apple and Huawei
with one external HTTP adapter in .NET, connected by configuration alone.

## What to check when you upgrade

**The keys of the channel buttons and the instruction have changed,** and the previous ones are gone
with no transition period. Move your own wording to the new key; the table is in
[What to check when you upgrade from 0.6.1](https://veriqa.app/docs/releases/0.7.md#what-to-check-when-you-upgrade-from-061).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.