CACHelp

Use CAC on Android

Read this before buying a reader: there is no working way to use a physical CAC in a card reader on Android. The supported path is a DISA Purebred derived credential on a government-managed device. ~20 min · 5 steps.

Stuck on a specific error? Describe it to the AI assistant for a tailored fix — or check our error code reference.

How CAC works on Android

This is the guide we would most like to be wrong about, so here is the reasoning rather than just the conclusion. Android has no smart card stack. There is no PC/SC layer and no CCID support anywhere in the platform — the operating system exposes only raw USB host transfers, which means any app wanting to talk to a CAC would have to implement the entire CCID protocol itself. Apple put that support in iOS 16; Google never did in Android.

For a while, apps filled the gap. Sub Rosa was the CAC-capable Android browser people recommended, built by Thursby Software Systems. Thursby was acquired by Identiv in 2018, and that business was sold to Vitaprotech in September 2024 and relaunched as Hirsch. Along the way the Android apps were withdrawn: both Sub Rosa Play Store listings now return 404, and thursby.com redirects to Hirsch, whose site no longer mentions the products at all. MilitaryCAC, the community reference this audience trusts most, states plainly as of its August 2026 update that it knows of no current apps that work with Android.

So a USB-C CCID reader plugged into an Android phone will enumerate as a USB device and then do nothing useful, because nothing on the phone can drive it. If a product listing or a blog claims a reader is 'compatible with Android' for CAC, it is describing the physical connector, not a working credential path. We are not listing reader models for Android for exactly this reason.

What does work is DISA Purebred, and it works by never involving the card. Purebred issues derived credentials — software certificates derived from your CAC under NIST SP 800-157 — into the Android KeyStore. The catch is eligibility: the Purebred Registration app is distributed only through an MDM, enrollment requires a live Purebred Agent and NIPRNet reachability, and the supported configurations are corporate-owned managed devices. If you have a personal Android phone and no organizational MDM, there is currently no path, and the honest answer is to use a computer or an iPhone instead.

What you need

  • A government-managed Android device — Purebred enrollment through Intune is documented for Android Enterprise corporate-owned fully managed and corporate-owned work profile devices. Personally-owned work profile is not a supported configuration, and a fully personal phone has no path at all.
  • A Purebred Agent in your organization — You cannot self-enroll. A live agent has to provision the credential, and the registration app is delivered through your MDM rather than the Play Store.
  • NIPRNet reachability — The Purebred portal is reachable from a NIPRNet workstation or over an appropriate VPN; it does not resolve from the public internet. Enrollment involves logging in there with your CAC to generate a one-time passcode.
  • Your CAC and a workstation with a reader — The card is used once, at a NIPRNet workstation, to prove identity and generate the OTP. It never touches the phone.

Steps

  1. 1

    Confirm which path applies to you

    If your phone is government-furnished or enrolled in your organization's MDM, continue with Purebred below. If it is a personal device with no MDM, stop here: there is no supported way to use a CAC with it, and buying a reader will not change that. Use a computer, or an iPhone with a USB-C CCID reader, which does work natively.

    • This is the step that saves money. The most common Android CAC mistake is buying a reader first and discovering afterwards that no software can use it.
  2. 2

    Ask your organization about Purebred eligibility

    Contact your mobility program office or help desk and ask whether they run DISA Purebred and whether your device qualifies. They will tell you how the Purebred Registration app is delivered to your phone — it is pushed through the MDM, and it is not available on the Play Store under any name.

    • Searching the Play Store for 'Purebred' will not find the official app. Do not install something because the name looks close.
    • Microsoft's own Intune documentation is internally inconsistent here: one setup screen labels the derived-credential issuer 'DISA Purebred (iOS only)' while the same documentation set describes an Android Enterprise Purebred workflow. Confirm with your mobility program rather than assuming either way.
  3. 3

    Enroll the device with a Purebred Agent

    From a NIPRNet workstation, log into the Purebred portal with your CAC, identify your device by serial number under My Devices, and generate a one-time passcode. Enter that OTP in the Purebred Registration app on the phone. The certificates are issued into the Android KeyStore, where other apps can reference them by alias.

    • Android 8.0 or later is the documented minimum for the Purebred enrollment flow.
    • The card is only used at the workstation. Nothing is ever plugged into the phone.
  4. 4

    Install the DoD root certificates (only if you need them)

    Go to Settings, then Security & privacy → Encryption & credentials → Install a certificate → CA certificate, and install the DoD roots from the DISA bundle. Menu wording varies by manufacturer and Android version, so treat that path as approximate. Note that many public DoD websites no longer need this at all — cyber.mil and the DMDC sites present commercially issued certificates from Let's Encrypt and DigiCert.

    • Certificates you install this way land in the user store, not the system store. Apps targeting Android 7.0 (API 24) and later ignore the user store unless their developer explicitly opted in, so this will not fix certificate errors in Outlook, a VPN client, or most third-party apps.
    • Chrome on Android does honour manually installed roots, which is why this step still helps for browsing DoD-issued TLS endpoints.
    • On Android 14 and later the system certificate store is immutable even with root access. Trusting a root across all apps requires an MDM-delivered certificate profile — there is no user-side equivalent.
  5. 5

    Use the credential in Chrome and your mail app

    Chrome on Android can present a client certificate that lives in the Android KeyStore, so a Purebred derived credential works for certificate-based authentication to .mil sites. This is the one area where Android is ahead of iOS: Safari and Edge on iOS cannot use an on-device certificate this way.

    • Chrome on Android cannot use a smart card — only an on-device certificate. Microsoft's Entra certificate-based authentication matrix states this explicitly.
    • For S/MIME, both Outlook for Android and Workspace ONE Boxer can sign and encrypt using a derived credential, but which combination is supported depends on your MDM. Outlook mobile sends clear-signed messages only, and the certificate's subject or SAN must match your primary SMTP address exactly or it will report that no certificate is available.

Verify it worked

  • Open a CAC-protected .mil site in Chrome — Chrome offers your derived credential in a certificate chooser. If no certificate is offered, the credential is not in the KeyStore — that is a Purebred enrollment problem, not a browser setting.
  • Look for the Purebred Registration app on the device — It is present because your MDM pushed it. If it is not there and your administrator says it should be, the MDM assignment has not applied yet.
  • Send a signed test message from your mail client — The message sends clear-signed. 'No certificate available' almost always means the certificate address does not exactly match your primary SMTP address.

Common problems

I bought a USB-C CAC reader and nothing happens

Expected. Android has no PC/SC or CCID stack, so no application can communicate with the card even though the reader enumerates over USB. There is no setting or app that fixes this. Listings claiming Android compatibility are describing the connector.

Sub Rosa is not in the Play Store

It was withdrawn. Both listings return 404 and the vendor chain ended at Hirsch, which no longer offers the product. There is no current replacement — MilitaryCAC's mobile page says the same as of August 2026.

A guide told me to install 'TF Maverick'

We could not find any evidence that a product by that name exists. Do not go looking for it, and be wary of the rest of any guide that recommends it.

Installed DoD roots but apps still show certificate errors

User-installed certificates are ignored by apps targeting Android 7.0 and later unless the developer opted in. Chrome honours them, but Outlook, VPN clients and most third-party apps will not. App-wide trust requires an MDM-delivered certificate profile.

USB accessories stop working when the screen is locked

Not CAC-specific, but worth knowing: Android 15's Lockdown mode disables USB data, and Android 16's Advanced Protection blocks USB data while locked and refuses new peripherals until you unlock and reconnect.

OTG seems disabled on my phone

Managed devices can have USB host functionality restricted by MDM policy — on Samsung devices this is a Knox restriction an administrator controls. Reports of consumer-facing OTG toggles are common in forums but we could not confirm them in manufacturer documentation. Either way this does not enable CAC use, since the software layer is what is missing.

Purebred enrollment fails at the OTP step

The passcode is generated on the Purebred portal from a NIPRNet workstation and is time-limited, and the device must be able to reach DoD infrastructure. If the portal is unreachable you are off NIPRNet — that is the usual cause.

Frequently asked questions

Can I use a CAC reader with my Android phone?

No. Android provides only a raw USB host API, with no PC/SC layer and no CCID support, so there is nothing for an app to read the card through. The apps that used to implement this themselves have all been withdrawn. A reader will physically connect and then do nothing.

What happened to Sub Rosa?

It was a genuine CAC-capable Android browser from Thursby Software Systems. Thursby was acquired by Identiv in 2018, that business was sold to Vitaprotech in September 2024 and became Hirsch, and the Android apps were withdrawn — both Play Store listings return 404 today and Hirsch's site no longer lists them.

So how do people actually use DoD credentials on Android?

Through DISA Purebred derived credentials on a government-managed device. Purebred issues software certificates derived from your CAC into the Android KeyStore, so the phone never needs to read the card. It requires an MDM, a Purebred Agent, and NIPRNet access to enroll.

Can I get Purebred on a personal phone?

No. The Purebred Registration app is distributed through an organization's MDM and is not published on the Play Store, and the supported Android Enterprise configurations are corporate-owned. Personally-owned work profile is not supported.

Is Android really worse than iOS for this?

For CAC specifically, yes, and the reason is architectural: Apple shipped native smart card support in iOS 16 while Android has no equivalent. There is one area where Android is ahead — Chrome on Android can authenticate with an on-device client certificate, which Safari and Edge on iOS cannot do.

Do I need to install DoD root certificates on Android?

Less often than you would think. Public DoD sites such as cyber.mil and the DMDC portals now present commercially issued certificates. DoD roots still matter for DoD-issued TLS endpoints and for validating a derived credential chain, but user-installed roots are ignored by most apps anyway.

What should I do right now if I just need to get into webmail?

Use a computer with a reader, which is the fully supported path on Windows, macOS and Linux, or an iPhone or iPad with a USB-C CCID reader, which works natively without any extra app. Both are faster than waiting for an Android solution that does not currently exist.

Official sources

Other platforms