Jami
  • Setup Jami
    • Download and install Jami
      • Jami for Android
      • Jami for GNU/Linux
      • Jami for iOS
      • Jami for macOS
      • Jami for Windows
      • Jami for servers
      • Jami for Web
    • Accounts
    • Add yourself
    • Link devices
    • Back up JAMI protocol accounts
    • Jami extensions
      • Jami extensions for Android
      • Jami extensions for Desktop
      • Jami extensions for iOS
      • Jami extensions for Web
  • Media
    • Safe software
    • Press releases
      • February 22, 2019
  • Videos
    • This is Jami
      • Let’s talk freely with Jami
      • How to talk privately with Jami
    • Jami for professionals
      • How can professionals communicate privately with their clients?
    • Jami for education
      • How can teachers communicate securely online with their students?
    • Jami for Windows
      • How to install Jami on Windows
    • Jami for macOS
      • How to create a Jami account on macOS
    • Jami for Android
      • How to create a Jami account on Android
    • Jami for Android TV
      • Use Jami on Android TV
    • JAMS (Jami Account Management Server)
      • Install JAMS on a server using Ubuntu 20.04 on a Digital Ocean Droplet
    • Tips
      • Why back up your Jami account?
      • How to share your ID on Android and iOS with other users (short version)
      • How to share your ID on Android and iOS with other users (long version)
      • How to configure biometric authentication for new accounts on Android
  • Recommendations
    • ar-AE العربية (الإمارات العربية المتحدة)
    • de-AT Deutsch (Österreich)
    • de-CH Deutsch (Schweiz)
    • de-DE Deutsch (Deutschland)
    • en-AU English (Australia)
    • en-CA English (Canada)
    • en-CH English (Switzerland)
    • en-DE English (Germany)
    • en-EC English (Ecuador)
    • en-GB English (United Kingdom)
    • en-ID English (Indonesia)
    • en-IN English (India)
    • en-IS English (Iceland)
    • en-KN English (Saint Kitts and Nevis)
    • en-SE English (Sweden)
    • en-US English (United States)
    • es-ES español (españa)
    • es-US español (estados unidos)
    • fr-BE Français (Belgique)
    • fr-CA Français (Canada)
    • fr-FR Français (France)
    • hi-IN हिंदी (भारत)
    • hu-HU magyar (Magyarország)
    • ko-KR 한국어(한국)
    • nl-NL Nederlands (Nederland)
    • pl-PL polski (Polska)
    • pt-BR Português (Brasil)
    • ru-RU Русский (Россия)
    • sv-SE svenska (Sverige)
    • tr-TR Türkçe (Türkiye)
    • vi-VN Tiếng Việt (Việt Nam)
    • zh-CN 中文(簡體,中國)
    • zh-TW 中文(繁體,台灣)
    • zh-US 中文(簡體,美國)
  • Учебно пособие за ползвателя
    • Введение
      • Как работи Джами?
      • Кой прави Джами?
    • Създаване на акаунт Jami
      • Android
      • iOS
      • macOS
      • Прозорци
    • Джами разпространена мрежа
      • Свързаност
      • Мрежата OpenDHT
      • Блокчейнът на JamiNS
    • Всички функции по клиент
      • Legend
      • Текстово съобщение
      • Обаждане
      • Настройки на сметката
      • Други характеристики
      • Разширени настройки
    • Часто задавани въпроси
      • Основи
      • Управление на сметките
      • Разширени
    • Използвайте Jami в LAN
      • Bootstrapping
      • TURN server
      • На мобилен телефон (DHT Proxy)
      • Именен сървър
    • Jami for servers
      • Create a user account on the server
      • Install the Jami daemon on the server
      • Copy the Jami configuration files
      • Create a script file to launch Jami on the server
    • Указател за докладване на бъгове
      • Определете средата си
      • Как да докладвате бъг
      • Написане на ясен обобщение
      • Написане на точни стъпки за възпроизвеждане
      • Получен резултат
      • Очаквания резултат
      • Предоставяне на допълнителна информация
  • JAMS manual
    • Download JAMS manual
    • Additional guides
      • Admin guide
      • Client guide
    • Introduction
      • Obtaining JAMS
      • System requirements
      • JAMS concepts
      • Getting started
      • Step 1: Create an administrator account
      • Step 2: Set up the Certification Authority
      • Step 3: Set up the user database
      • Step 4: Set up the server parameters
    • Private DHT node
  • Изграждане на ръководство
    • Sections
      • Введение
      • Зависимости
  • Учебно пособие за разработчиците
    • Заявки за характеристики
      • СФЛ
      • Планирани/В процес
      • Искано, но не планирано
      • Може да бъде реализирана, приветствани вноски (или ще отнеме месеци/години)
      • Зависи от промените в масата
      • Опаковки
      • Други
    • New developers
      • АПИ на Джами
      • Стиль на кодиране
      • Debugging tools
      • Подобряване на качеството на Jami
      • Стил на кодиране Qt и QML
      • Инструменти за изпитване на Qt и QML
      • Предавам първия си пласт
      • Работа с Джъррит
    • Jami Concepts
      • Управление на сметките
      • Звук
      • Забраняваните контакти
      • Обаждания
      • Обаждания в Сварм
      • Протокол на конференцията
      • Управляващият връзка
      • Управление на контактите
      • Dynamic Routing Table (DRT)
      • Прехвърляне на файлове
      • Идентификатори на Jami
      • Свържете ново устройство
      • Нарича се протокол на сървъра
      • Сбор
      • Протокол за синхронизация
      • Синхронизация на профила
    • Going further
      • Избор на стойността CRF за кодиране
      • Synchronization of delivery status
      • How it works (backend)
      • Client API
      • Notes for client
      • Важни РФК
      • Местоположение Споделяне на QT клиент
      • Състояние на показваното съобщение
      • Настройка на свой собствен сървър
    • Processes
      • Design Process
      • Процес на освобождаване
  • Extension manual
    • How it works?
      • How to use it?
      • Setup
      • Android
      • Linux/Windows
      • Use!
    • How to build?
      • Dependencies
      • ONNX Runtime 1.6.0
      • Plugin
    • Publishing on the Extension Store
      • Publication on the Extension Store
      • How the Extension Store works in Jami Desktop
      • Important: Test locally before publication
      • Add an extension
      • Congratulations, the Jami Extension has been added and is available for Jami users!
    • Creating Jami extensions
      • Jami extensions
    • Jami extension certificates
      • Certificates
      • Signature mechanism
      • Certificate chain
      • Certificate constraint
      • Certificate revocation
      • Sign an organization certificate
      • Create certificate
      • Sign an extension
      • Revoke a certificate
      • Verify certificate
      • Example
    • Extension Store in the Jami client
      • The Extension Store in the Daemon
      • The Extension Store in the Client
      • Extension State
    • TensorFlow extension
      • TensorFlow 2.1.0
  • Принос
    • Отчитане на грешки и проблеми
    • Код за участие
    • Commit message guidelines
    • Пакетиране Jami
    • Принос към тази документация
    • Зависимости
    • Клониране на хранилището
    • Редактиране на страница
    • Преглед на работата си
    • Да спасяваш работата си
    • Предаване на промяна
    • Промяна на работата си
    • Добавяне на страница
  • GNU Free Documentation License
    • 0. PREAMBLE
    • 1. APPLICABILITY AND DEFINITIONS
    • 2. VERBATIM COPYING
    • 3. COPYING IN QUANTITY
    • 4. MODIFICATIONS
    • 5. COMBINING DOCUMENTS
    • 6. COLLECTIONS OF DOCUMENTS
    • 7. AGGREGATION WITH INDEPENDENT WORKS
    • 8. TRANSLATION
    • 9. TERMINATION
    • 10. FUTURE REVISIONS OF THIS LICENSE
    • 11. RELICENSING
    • ADDENDUM: How to use this License for your documents
Jami
  • Учебно пособие за разработчиците
  • Jami Concepts
  • Свържете ново устройство
  • View page source

Свържете ново устройство

This document describes the architecture of the feature allowing users to link their account to a new device, referred to as the Link new device process.

  • Terminology

  • State machine

    • State overview

    • Подробности

      • Details for import side

      • Details for export side

  • API between daemon and client

    • API for import side

    • API for export side

  • Daemon state machine

  • Client state machine

  • Full sequence diagram (import and export)

Terminology

To understand this document, here are some key terms:

  • import side: The device importing the account.

  • export side: The device exporting the account.

  • token: A URI that identifies a device on the Distributed Hash Table (DHT).

State machine

The daemon manages this functionality using a state machine.

The state evolution is communicated to clients, enabling the appropriate interface display.

Currently, the state machine is symmetrical for both import side and export side, though certain states are inaccessible depending on the side.

State overview

Състояние

Име

Usage (Side)

Описание

0

Init

Нито една.

Initial state.

1

Token available

Import only

The token is available. This is the URI identifying the new device on the DHT, displayed as text or a QR code.

2

Свързване

Export/Import

A peer-to-peer connection is being established.

3

Authenticating

Export/Import

The identity of the account and device address are being confirmed.

4

In progress

Export/Import

State transition, the account archive is being transferred.

5

Готово

Export/Import

Final state. Represents success or failure.

Подробности

The state machine can include supplementary information for display purposes, passed as a map<String, String> called details.

Details for import side

Състояние

Име

Подробности

0

Init

Not applicable.

1

Token available

token: A 59-character URI with the prefix jami-auth://.

2

Свързване

No details.

3

Authenticating

peer_id: Jami ID of the imported account.
auth_scheme: {"", "none", "password"} (empty if unprotected).
auth_error: {"bad_password"}.

4

In progress

No details.

5

Готово

error: {"", "none", "network", "authentication"} (empty if no error).

Details for export side

Състояние

Име

Подробности

0

Init

Not applicable.

1

Token available

Not applicable.

2

Свързване

No details.

3

Authenticating

peer_address: IP address of the exporting device.

4

In progress

No details.

5

Готово

error: {"", "none", "network", "authentication"} (empty if no error).

API between daemon and client

API for import side

Signal Name

Direction

Purpose

addAccount

Outbound

Announces the intent to import an account. Must include the key Account.archiveURL="jami-auth".

provideAccountAuthentication

Outbound

Provides a password if needed and confirms the identity of the imported account.

removeAccount

Outbound

Cancels the operation.

deviceAuthStateChanged

Inbound

Indicates the new state and provides details.

API for export side

Signal Name

Direction

Purpose

addDevice

Outbound

Announces the intent to export an account.

confirmAddDevice

Outbound

Confirms the address of the exporting device.

cancelAddDevice

Outbound

Cancels the operation.

addDeviceStateChanged

Inbound

Indicates the new state and provides details.

Daemon state machine

        stateDiagram-v2
    state "Import Side" as Import {
        [*] --> Import_Init
        Import_Init --> Import_TokenAvailable: Generate token
        Import_TokenAvailable --> Import_Connecting: Peer detected
        Import_Connecting --> Import_Authenticating: Connection established
        Import_Authenticating --> Import_InProgress: Auth success
        Import_InProgress --> Import_Done: Transfer complete
        note right of Import_TokenAvailable
            Provides:
            - Authentication code
            - QR data
        end note
        note right of Import_Authenticating
            May require password
            auth_scheme: "", "none", "password"
        end note
        note right of Import_Done
            error: "", "none", "network", "authentication"
        end note
    }
    state "Export Side" as Export {
        [*] --> Export_Init
        Export_Init --> Export_Connecting: Token validated
        Export_Connecting --> Export_Authenticating: Connection established
        Export_Authenticating --> Export_InProgress: Auth success
        Export_InProgress --> Export_Done: Transfer complete
        note right of Export_Init
            Accepts:
            - Authentication code
            - QR data
        end note
        note right of Export_Authenticating
            Confirms peer address
        end note
    }
    

Client state machine

        stateDiagram-v2
    [*] --> Initial
    Initial --> ImportDevice: ImportFromDevice selected
    Initial --> ExportDevice: ExportToDevice selected
    state "Import Device" as ImportDevice {
        [*] --> Import_Init
        Import_Init --> Import_TokenAvailable: Token received
        Import_TokenAvailable --> Import_Connecting: Peer detected
        Import_Connecting --> Import_Authenticating: Connection established
        Import_Authenticating --> Import_InProgress: Auth success
        Import_InProgress --> Import_Done: Transfer complete
        Import_Authenticating --> Import_Error: Bad password
        Import_Connecting --> Import_Error: Connection failed
        Import_InProgress --> Import_Error: Transfer failed
        Import_Error --> [*]: Reset
        Import_Done --> [*]: Account ready
        note right of Import_TokenAvailable
            Display:
            - QR code
            - Authentication code
            - Copy button
        end note
        note right of Import_Authenticating
            Show password input if needed
        end note
    }
    state "Export Device" as ExportDevice {
        [*] --> Export_Init
        state Export_Init {
            [*] --> ShowInputOptions
            ShowInputOptions --> ScanQR: Camera selected
            ShowInputOptions --> ManualEntry: Manual selected
            ScanQR --> QRScanning: Start camera
            QRScanning --> TokenObtained: QR detected
            QRScanning --> ShowInputOptions: Cancel scan
            ManualEntry --> TokenObtained: Valid code entered
            ManualEntry --> ShowInputOptions: Cancel entry
        }
        Export_Init --> Export_Connecting: Token validated
        Export_Connecting --> Export_Authenticating: Connection established
        Export_Authenticating --> Export_InProgress: Auth provided
        Export_InProgress --> Export_Done: Transfer complete
        Export_Connecting --> Export_Error: Invalid token
        Export_Authenticating --> Export_Error: Auth failed
        Export_InProgress --> Export_Error: Transfer failed
        Export_Error --> [*]: Reset
        Export_Done --> [*]: Device added
        note right of Export_Init
            Input options:
            - QR scanner
            - Manual code entry
        end note
        note right of Export_Authenticating
            Confirm peer device
        end note
    }
    ImportDevice --> Initial: Back/Cancel
    ExportDevice --> Initial: Back/Cancel
    

Full sequence diagram (import and export)

        sequenceDiagram
    box white Import Side
    participant IC as New Client
    participant ID as New Daemon
    end
    box white Export Side
    participant ED as Old Daemon
    participant EC as Old Client
    end
    %% Initial Setup
    IC->>ID: addAccount(archiveURL="jami-auth")
    activate ID
    ID-->>IC: deviceAuthStateChanged(state=TOKEN_AVAILABLE)
    Note over IC: Display QR code<br/>and auth token
    %% Export Side Initiation
    EC->>EC: User chooses to export
    EC->>EC: Scan QR/Enter token
    EC->>ED: addDevice(token)
    activate ED
    %% Connection Establishment
    ED->>ID: DHT connection request
    ID-->>IC: deviceAuthStateChanged(state=CONNECTING)
    ED-->>EC: addDeviceStateChanged(state=CONNECTING)
    %% Authentication Phase
    ID-->>IC: deviceAuthStateChanged(state=AUTHENTICATING,<br/>peer_id, auth_scheme)
    ED-->>EC: addDeviceStateChanged(state=AUTHENTICATING,<br/>peer_address)
    alt Account is password protected
        IC->>IC: Show password prompt
        IC->>ID: provideAccountAuthentication(password)
    end
    EC->>ED: confirmAddDevice()
    %% Transfer Phase
    ID-->>IC: deviceAuthStateChanged(state=IN_PROGRESS)
    ED-->>EC: addDeviceStateChanged(state=IN_PROGRESS)
    ED->>ID: Transfer account archive
    %% Completion
    ID-->>IC: deviceAuthStateChanged(state=DONE, error="")
    ED-->>EC: addDeviceStateChanged(state=DONE, error="")
    deactivate ID
    deactivate ED
    Note over IC,EC: Account successfully linked
    alt Error Scenarios
        ID-->>IC: deviceAuthStateChanged(state=DONE, error="network")
        ED-->>EC: addDeviceStateChanged(state=DONE, error="network")
        Note over IC,EC: Network error during transfer
        ID-->>IC: deviceAuthStateChanged(state=DONE, error="authentication")
        ED-->>EC: addDeviceStateChanged(state=DONE, error="authentication")
        Note over IC,EC: Authentication failed
    end
    %% Cancellation Scenarios
    rect rgb(240, 240, 240)
        Note over IC,EC: Optional Cancellation Flows
        IC->>ID: removeAccount()
        EC->>ED: cancelAddDevice()
    end
    
Previous Next

Правителство за авторски права © 2018-2025 Savoir-faire Linux Inc. and contributors.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.

Built with Sphinx using a theme provided by Read the Docs.