at_onboarding_cli 1.16.0

Dart tools for initial client onboarding, subsequent client enrollment, and enrollment management.

at_onboarding_cli

CLI-side wrapper around at_auth that provides the command-line tooling end users and CLI apps need to register, onboard, and enroll atSigns — plus a library surface for building your own onboarding tooling.

If you're new to the Atsign Protocol lifecycle (register → onboard → APKAM enroll), read at_auth's README first — this package is the CLI concretisation of that model. at_client_flutter is the Flutter-UI equivalent.

Turnkey CLI tools

Both ship as executables when this package is globally activated:

dart pub global activate at_onboarding_cli

at_register — get a free atSign

at_register -e [e-mail]

Fetches a free atSign, emails you a verification code, then runs at_activate automatically once you paste the code back. The generated .atKeys file lands in ~/.atsign/keys/.

at_activate — onboard an atSign (Phase 2 of the lifecycle)

# Using a CRAM secret from email / registrar
at_activate -a @alice -c <cram_secret>

# OR using an email-delivered verification code
at_activate -a @alice

Either form produces the master .atKeys in ~/.atsign/keys/. These are the root of trust for @alice — back them up.

APKAM enrollment

A new device / app authenticating as an existing atSign should go through APKAM rather than asking the user for their master keys. The worked example lives under example/apkam_examples/:

• apkam_enroll.dart — the new device submits an enrollment request scoped to specific namespaces
• enroll_app_listen.dart — a device holding the master keys listens for and approves / denies incoming requests
• apkam_authenticate.dart — the new device authenticates with its newly-issued scoped keys

Full step-by-step walkthrough: example/README.md.

Library usage

If you're building your own onboarding tooling, AtOnboardingService is the main entry point:

import 'package:at_onboarding_cli/at_onboarding_cli.dart';

final pref = AtOnboardingPreference()
  ..rootDomain = 'root.atsign.org'
  ..namespace = 'my_app'
  ..hiveStoragePath = 'storage/hive'
  ..commitLogPath = 'storage/commitLog'
  ..isLocalStoreRequired = true
  ..atKeysFilePath = 'storage/@alice_key.atKeys';

final svc = AtOnboardingServiceImpl('@alice', pref);

// Onboard (Phase 2): CRAM-authenticate and generate master atKeys.
// Provide cramSecret via pref.cramSecret; omit to trigger email OTP.
await svc.onboard();

// Or, for a previously-onboarded atSign, just authenticate (Phase 3).
await svc.authenticate();

final AtClient? atClient = await svc.atClient;
final AtLookUp? atLookup = svc.atLookUp;

Worked examples covering each flow: example/ and example/legacy_examples/.

Most app developers don't need this library directly — they use at_cli_commons' CLIBase which calls AtOnboardingService internally.

Where to go next

• at_auth — the lifecycle model this package exposes via CLI
• at_cli_commons — thin layer that gets you from already-onboarded atKeys to an authenticated AtClient in one line
• at_client_flutter — the Flutter-UI equivalent of this package

Open source usage and contributions

BSD3-licensed. See CONTRIBUTING.md for guidance on setting up tools, running tests, and raising a PR.