Passkey
Uses Android Credential Manager and the phone's screen lock. The private credential remains protected by the device or credential provider.
Getting started
Prepare the phone, install the app, and sign in.
Use a supported Android phone and the application build approved for your Xibernetix environment. NFC device control requires physical NFC hardware and an operator account.
Before you begin
| Requirement | Why it is needed |
|---|---|
| Android 11 / API 30 or newer | The application supports Android 11 and later. Bluetooth scanning on Android 11 requires location permission and Location to be enabled. |
| Internet connection | Required for sign-in and first pairing, including account data and NFC key-diversification requests. Later supported operations can continue temporarily offline, but the app must reconnect periodically to synchronize ownership and lifecycle changes. |
| Screen lock | A PIN, pattern, password, or biometric unlock is normally required to create and use passkeys. |
| NFC-capable phone | Required only for NFC tag provisioning and authentication. Emulators generally cannot perform a real scan. |
| Authorized account | Maker, operator, and administrator workspaces expose different actions. |
Install and open the app
- Obtain the approved build.Use the Google Play listing or APK supplied by your administrator. Development, staging, and production builds connect to different environments; do not substitute one for another.
- Allow Android to install it.If an administrator supplies an APK, Android may ask for permission to install from that source. Only approve a package whose source and signing identity you trust.
- Open Xibernetix.Choose the workspace that matches your account: Maker, Operator, or Administrator.
- Sign in or sign up.Use an available sign-in method. New users should enter the profile details requested by their workspace and follow any passkey-registration prompt.
Use the correct environment. Accounts and NFC key records are environment-specific. A tag
provisioned against one backend may not authenticate in another environment.
Account and sign-in choices
Google sign-in
Uses the Google account chooser when enabled for the deployment. Select the account associated with your Xibernetix profile.
Deployment sign-in
Some builds can expose another configured sign-in form. Follow your organization's account and recovery policy.
Passkey setup
- Accept the passkey-registration prompt after an eligible sign-in or registration.
- Choose the Android credential provider if prompted.
- Confirm with the phone's screen lock or biometric sensor.
- Keep at least one approved recovery or alternative sign-in route available.
Prepare for NFC scanning
- Enable NFC.Open Android Settings and turn on NFC. The exact menu name differs by phone manufacturer.
- Remove obvious interference.Thick or metallic cases can reduce range. Find the phone's NFC antenna, usually near its top or center.
- Use an operator account.NFC Device Control rejects accounts without the operator role.
- Keep the network available.A tag whose diversified key is not cached requires a bounded backend lookup during the scan.