Android SDK#

The Curity HAAPI Android SDK sits on top of the Android Driver. It exposes HaapiManager for flow stepping and OAuthTokenManager for OAuth token lifecycle, wrapped together by HaapiAccessor. The Android UIWidget framework composes this SDK internally.

This page is a platform-specific entry point: install instructions, the per-language reference, and pointers to the shared topic pages.

Installation#

The Android SDK ships as its own Maven artifact. The Android Driver is automatically pulled in as a transitive dependency — you do not need to declare it separately.

dependencies {
    // Replace LATEST_VERSION with the latest release on Maven Central.
    implementation("se.curity.identityserver:identityserver.haapi.android.sdk:LATEST_VERSION")
}

The SDK requires Android 8.0 or later (API level 26+).

Code Reference#

The auto-generated Android SDK reference, with the full public API surface, lives at:

• https://curity.io/docs/haapi-android-sdk/latest/

For class-level documentation, signatures, and parameter lists, follow the link above. The pages below cover configuration and usage patterns.

Topic Pages#

Foundational#

• Creating a HaapiAccessor — HaapiAccessorFactory and the three access patterns
• HAAPI Flow — start → submit → followLink stepping and step models
• Android Representations — the HaapiResponse sealed hierarchy, the 14 step types, actions, form fields, and problems
• OAuthTokenManager — fetch, refresh, revoke

Configuration#

• Token Binding — TokenBoundConfiguration with a Storage implementation
• DCR — DcrConfiguration fallback for non-attestation devices
• Risk Assessment — applicationContext from Application.onCreate
• Client Authentication — wiring Secret, MTLS, or Signed JWT

Operational#

• Token Endpoint Response Listener — capture raw headers and JSON
• Error Handling — IdsvrHaapiException.Retryable / Unrecoverable and ErrorTokenResponse
• Logging — HaapiLogger.setLevel with Driver + SDK tag prefixes