Passkey
Uses Android Credential Manager and the phone's screen lock. The private credential remains protected by the device or credential provider.
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.
| Requirement | Why it is needed |
|---|---|
| Android 14 / API 34 or newer | The application currently declares API 34 as its minimum supported Android SDK. |
| Internet connection | Sign-in, account data, and NFC key-diversification requests use the Xibernetix backend. |
| 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. |
Uses Android Credential Manager and the phone's screen lock. The private credential remains protected by the device or credential provider.
Uses the Google account chooser when enabled for the deployment. Select the account associated with your Xibernetix profile.
Some builds can expose another configured sign-in form. Follow your organization's account and recovery policy.