Credential provider role (third party password and passkey manager)
An app registers as the person's password and passkey manager for the whole system.
In one line
Can act as your phone's password and passkey manager once you turn it on
An app registers as the person's password and passkey manager for the whole system.
The chosen manager can supply logins for every other app and site, and sees which services the person signs into. It is one of the most trusted roles on the phone.
What it can and can't do
What the user does: You open Settings and choose this app as your passwords and passkeys provider
It can
- Save passwords and passkeys that other apps and sites ask to store
- Offer matching logins when you sign in to another app or website
- Unlock a login after checking your fingerprint, face or master password
- Offer passkeys to other apps and sites on iPhone from iOS 17
It cannot
- Become your provider until you turn it on in Settings
- See logins stored by other providers
- Hand over a login without your approval on screen
- Work in apps that block autofill
How it differs between platforms: Android has a system role and a default provider choice. iPhone has an Autofill provider switch and added passkey support in iOS 17.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Behind a flag | Behind a flag |
| First version | Android 14 (API 34) | iOS 12.0 |
| Permission or entitlement | BIND_CREDENTIAL_PROVIDER_SERVICE | com.apple.developer.authentication-services.autofill-credential-provider |
| Protection level | signature | entitlement |
| How access is granted | role | settings |
| What the user sees | User picks provider in Settings > Passwords & accounts | Settings > General > AutoFill & Passwords picks apps |
| How long it lasts | Until changed | Until changed |
| How to take it back | Settings > Passwords, passkeys and accounts | Settings > AutoFill & Passwords |
| Store policy | Play: credential manager apps follow User Data policy | App Review 5.1 |
| API | CredentialProviderService (API 34), androidx.credentials.provider | ASCredentialProviderViewController, ASPasskeyCredentialIdentity (iOS 17), ASCredentialIdentityStore |
| Notes | Provider apps must be enabled by the user; Android 15 adds default-provider behaviors. | iOS 17 adds passkey providers; iOS 26 adds credential exchange. |
Data you get
What comes back: Credential list
Shape: object
How often: on request
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
identities | list | count | varies | exact |
Technical limits
- User chooses provider explicitly in Settings on both OS
The story
What it is
An app becomes your phone's main place for passwords and passkeys.
For you
You pick a manager in Settings and from then on it offers your logins in every app and website. You also see its name at sign in. It feels like one safe place for all your accounts.
For makers
For a password manager this role is the product: it is how its logins show up everywhere without copy and paste. It is also the most trusted job on a phone, because it can see which services you use.
Where you see it
| Type | Example | Apps |
|---|---|---|
| productivity | A password app fills your work login in a banking app, a news app and a browser, all from one unlock. | 1Password, Bitwarden, Dashlane |
| security | A manager shows you only the passkey for the real site and warns you that a look alike site has none saved. | None named |
| games | You sign back into a game on a new phone and your manager fills the login and the one time code in a single step. | None named |
| enterprise | A company rolls out one approved manager to staff phones so every work app signs in the same way. | None named |
| kids | A family plan lets a parent share one safe login with a child's phone without typing the password in front of them. | None named |
| banking | Your bank app asks to create a passkey, and your chosen manager stores it and syncs it to your tablet. | None named |
Risks
- Most trusted app role
- Malicious provider can harvest logins
Android and iPhone in short
- Android: Android treats this as a switch in Settings, and you can have more than one provider with one set as the main.
- iPhone: iPhone lets third party managers act as the system provider, and the user turns them on in Settings under Passwords.
What the platform says
- Google: Credential Manager providers. Android lets password managers plug in so you can sign in with passkeys and passwords from your chosen app.
- Apple: Passwords and passkeys providers. Apple lets other password apps supply logins and passkeys system wide, alongside its own Passwords app.
Good uses and abuse
Legitimate uses
- 1Password and Bitwarden type apps
Known abuse
- Malicious provider harvesting logins
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | 1 | Rough identifying entropy, when known |
History
- 2018-09, iPhone iOS 12: Password manager extensions as AutoFill providers
- 2023-09, iPhone iOS 17: Passkeys for third party providers
- 2023-10, Android 14 (API 34): Credential Manager and provider API
Related capabilities
Related
- Passkeys in an app (create and sign in). Can create and use passkeys inside the app after you approve with your device lock
- Autofill (app side and service side). Can offer saved logins, cards and addresses in forms, only after you tap a suggestion
Same idea on the web
- Credential Management (password and federated). Can fetch a saved login after you pick an account in a browser sheet
Sources
How well checked: Based on official documentation.