Swift SDK

The Swift account client is in swift/MesgdAuth.swift in mesgd-sdk. Use it to enroll an account, obtain a session, and manage public keys independently of the PKI layer. The examples use an existing account named alice; passwords and authenticator codes come from the application rather than literals in source.

Support status

The account adapter is available, but a built-in HTTPS transport is still pending. The transport argument in the examples is application code, not a missing SDK constructor.

Completeness position: 14 of 18. Account adapter and Apple-oriented cryptography; native HTTPS adapter, Linux RSA, and shared coverage remain pending. The language matrix explains the ranking criteria and comparable tiers. WSS readiness is listed separately; no SDK currently provides a complete, validated encrypted messaging workflow against this server.

Setup and transport

Add MesgdAuth.swift to the application's Swift target and import Foundation. Authentication uses dictionaries and Swift concurrency. The separate PKI sample targets Apple platforms; its RSA path is not implemented for Linux.

Supply a MesgdAuth.Transport closure taking method, path, optional body, and optional bearer. It asynchronously returns (Int, [String: Any]). The application owns its URLSession configuration and must retain normal certificate checks, reject redirects, and set a timeout.

A custom transport must serialize JSON, attach Authorization: Bearer TOKEN only when a token is supplied, verify the certificate and hostname, reject redirects, and use a finite timeout. Its origin is an HTTPS URL, such as https://mesgd.example.com, rather than a WebSocket URL.

Log in, read keys, and log out

Pass the current authenticator code as a six-digit string, preserving leading zeroes. This example reads the account's published keys and ends the session on its successful path. Applications that retain a session can keep the bearer until logout or expiry instead.

import Foundation

func readKeys(transport: @escaping MesgdAuth.Transport,
              password: String, otp: String) async throws -> [String: Any] {
    let client = MesgdAuth(transport: transport)
    let session = try await client.login("alice", password, otp)
    guard let token = session["access_token"] as? String else {
        throw MesgdAuthError.invalidInput
    }
    let keys = try await client.publicKeys(token)
    _ = try await client.logout(token)
    return keys
}

HTTP failures throw MesgdAuthError.http(status); malformed OTPs and rejected public-key input throw .invalidInput. The GET-key operation is named publicKeys, while the corresponding operation in several other languages is named keys.

Enroll a new account

The following fragment uses an existing client or transport from the example above. Signup returns a pending enrollment. Display qr_png_base64 or otpauth_uri, let the person configure the authenticator, then collect a code to confirm it. These calls are separate application steps, with user interaction between them.

let enrollment = try await client.signup("alice", "alice@example.com", password)
// Display enrollment before collecting enrollmentOTP.
guard let enrollmentToken = enrollment["enrollment_token"] as? String else {
    throw MesgdAuthError.invalidInput
}
let session = try await client.confirm("alice", enrollmentToken, enrollmentOTP)
let recoveryCodes = session["recovery_codes"]

Confirmation returns the first session and eight recovery codes. Display the recovery codes for separate safekeeping. A code accepted for confirmation cannot be reused for login or a key update; wait for a new authenticator step before another operation that consumes a code.

Account operations

A key update takes the session token, current password, a fresh authenticator code, and an array containing only public JWKs. An empty array clears the linked keys. A password reset takes the username, a saved recovery code, a new password, and a fresh authenticator code; success replaces the recovery codes and revokes existing sessions without returning a new session.

The shared authentication reference documents argument order, response fields, and transport behavior. Session refresh is available through the HTTP API but is not wrapped by these seven SDK operations.

Message connections

Account login does not establish a message connection. The current server accepts JSON WebSocket frames and can authenticate an upgrade with a login session or an issued grant token. Login sessions carry identity without path restrictions; grants limit routing to assigned patterns. See WebSocket and Routing.

The encrypted registration handshake in the ping/pong samples is not implemented by the current mesgd listener. Treat those samples as experimental cryptographic examples, with compatibility limits described in Samples.

Validation

This account module is not included in the shared auth contract runner. Check it with the application's own toolchain and transport before deployment. The presence of source examples does not imply that live HTTPS or cross-language cryptographic behavior has been validated for this implementation. Languages lists the repository's current test coverage.