Using the Keychain to Manage User Secrets

Relieve the user of remembering small secrets by storing them in the keychain.


Apps often need access to sensitive user data such as passwords, but keeping the data secure can come at a cost: If you store a data without encrypting it, you create a security risk. If instead you repeatedly prompt the user, you produce a bad user experience—one that typically causes the user to create simple passwords or else write them down.

Keychain services helps solve this problem by providing easy access to encrypted storage. Your app uses the keychain, along with minimal user interaction, to provide a good user experience. For example, consider a process like the one depicted in Figure 1 for storing an Internet password.

Figure 1

Using a keychain item to store an Internet password

A flow diagram that depicts a process for using a keychain item when possible to authenticate against a server, and prompting the user when the keychain item is not found or is out of date.

Involve the User When Needed

The first time an app needs credentials, no password is stored in the keychain. Here, the app prompts the user, as shown in the right branch of the diagram.

After the user has provided credentials that successfully authenticate, the app stores them using a call to the SecItemAdd function. The app now continues with its regular network access. Later, when the server requires reauthentication, the app can retrieve the credentials from the keychain instead of bothering the user.

For additional information about how to add items to the keychain, see Adding a Password to the Keychain.

Avoid Bothering the User in the Common Case

The most common path through the diagram is the central one, which requires no user interaction. Here, a secure network resource requires periodic reauthentication, for example, because the user relaunches an app after having been away for a while.

In response, the app searches the keychain for the password, using the SecItemCopyMatching function. If the password is found and the app successfully uses it to authenticate, it’s free to continue without involving the user.

For details about conducting a search, see Searching for Keychain Items.

Handle Changes Gracefully

Occasionally, the user changes credentials outside the scope of the app. For example, you might offer a web interface to the same service that allows the user to change or reset their password. In this situation, a subsequent keychain item search in the app produces an out-of-date password that fails to authenticate. The left branch of the flow diagram handles this scenario. As with the right branch, the app prompts the user for new credentials. But in this case the app uses a call to the SecItemUpdate function to modify the existing stored value after validating the new credentials.

The user might also decide to disconnect entirely from the network service. In response, your app should “forget” the corresponding credentials, along with performing any other actions required to log out. Use the SecItemDelete function to remove the password from the keychain entirely.

For a discussion about changing and removing existing items, see Updating and Deleting Keychain Items .


Item Creation and Modification

Adding a Password to the Keychain

Add network credentials to the keychain on behalf of the user.

Searching for Keychain Items

Find keychain items based on search criteria that you specify.

Updating and Deleting Keychain Items

Modify items in the keychain when the user’s data changes.

Item Access

Sharing Access to Keychain Items Among a Collection of Apps

Enable apps to share keychain items with each other by adding the apps to an access group.

Restricting Keychain Item Accessibility

Set the conditions under which an app can access a keychain item such as a password.

See Also

First Steps


An opaque type that represents a keychain item.


Returns the unique identifier of the opaque type to which a keychain item object belongs.