Valet lets you securely store data in the iOS, tvOS, watchOS, or macOS Keychain without knowing a thing about how the Keychain works. It’s easy. We promise.
Install with CocoaPods by adding the following to your
platform :ios, '9.0' use_frameworks! pod 'Valet'
platform :tvos, '9.0' use_frameworks! pod 'Valet'
platform :watchos, '2.0' use_frameworks! pod 'Valet'
platform :osx, '10.11' use_frameworks! pod 'Valet'
Install with Carthage by adding the following to your
carthage to build the framework and drag the built
Valet.framework into your Xcode project.
Swift Package Manager
Install with Swift Package Manager by adding the following to your
dependencies: [ .package(url: "https://github.com/Square/Valet", from: "3.0.0"), ],
Or manually checkout the submodule with
git submodule add email@example.com:Square/Valet.git, drag Valet.xcodeproj to your project, and add Valet as a build dependency.
let myValet = Valet.valet(with: Identifier(nonEmpty: "Druidia")!, accessibility: .whenUnlocked)
VALValet *const myValet = [VALValet valetWithIdentifier:@"Druidia" accessibility:VALAccessibilityWhenUnlocked];
To begin storing data securely using Valet, you need to create a Valet instance with:
- An identifier – a non-empty string that is used to identify this Valet. The Swift API uses an
Identifierwrapper class to enforce the non-empty constraint.
- An accessibility value – an enum (Accessibility) that defines when you will be able to persist and retrieve data.
myValet instance can be used to store and retrieve data securely on this device, but only when the device is unlocked.
Choosing the Best Accessibility Value
The Accessibility enum is used to determine when your secrets can be accessed. It’s a good idea to use the strictest accessibility possible that will allow your app to function. For example, if your app does not run in the background you will want to ensure the secrets can only be read when the phone is unlocked by using
Reading and Writing
let username = "Skroob" myValet.set(string: "12345", forKey: username) let myLuggageCombination = myValet.string(forKey: username)
NSString *const username = @"Skroob"; [myValet setString:@"12345" forKey:username]; NSString *const myLuggageCombination = [myValet stringForKey:username];
In addition to allowing the storage of strings, Valet allows the storage of
Data objects via
set(object: Data, forKey key: Key) and
-objectForKey:. Valets created with a different class type, via a different initializer, or with a different accessibility attribute will not be able to read or modify values in
Sharing Secrets Among Multiple Applications
let mySharedValet = Valet.sharedAccessGroupValet(with: Identifier(nonEmpty: "Druidia")!, accessibility: .whenUnlocked)
VALValet *const mySharedValet = [VALValet valetWithSharedAccessGroupIdentifier:@"Druidia" accessibility:VALAccessibilityWhenUnlocked];
This instance can be used to store and retrieve data securely across any app written by the same developer with the value
Druidia under the
keychain-access-groups key in the app’s
Entitlements file, when the device is unlocked. Note that
mySharedValet can not read or modify one another’s values because the two Valets were created with different initializers. All Valet types can share secrets across applications written by the same developer by using the
Sharing Secrets Across Devices with iCloud
let myCloudValet = Valet.iCloudValet(with: Identifier(nonEmpty: "Druidia")!, accessibility: .whenUnlocked)
VALValet *const myCloudValet = [VALValet iCloudValetWithIdentifier:@"Druidia" accessibility:VALAccessibilityWhenUnlocked];
This instance can be used to store and retrieve data that can be retrieved by this app on other devices logged into the same iCloud account with iCloud Keychain enabled. If iCloud Keychain is not enabled on this device, secrets can still be read and written, but will not sync to other devices. Note that
myCloudValet can not read or modify values in either
myCloudValet was created a different initializer.
Protecting Secrets with Face ID, Touch ID, or device Passcode
let mySecureEnclaveValet = SecureEnclaveValet.valet(with: Identifier(nonEmpty: "Druidia")!, accessControl: .userPresence)
VALSecureEnclaveValet *const mySecureEnclaveValet = [VALSecureEnclaveValet valetWithIdentifier:@"Druidia" accessControl:VALAccessControlUserPresence];
This instance can be used to store and retrieve data in the Secure Enclave. Each time data is retrieved from this Valet, the user will be prompted to confirm their presence via Face ID, Touch ID, or by entering their device passcode. If no passcode is set on the device, this instance will be unable to access or store data. Data is removed from the Secure Enclave when the user removes a passcode from the device. Storing data using
SecureEnclaveValet is the most secure way to store data on iOS, tvOS, watchOS, and macOS.
let mySecureEnclaveValet = SinglePromptSecureEnclaveValet.valet(with: Identifier(nonEmpty: "Druidia")!, accessControl: .userPresence)
VALSinglePromptSecureEnclaveValet *const mySecureEnclaveValet = [VALSinglePromptSecureEnclaveValet valetWithIdentifier:@"Druidia" accessControl:VALAccessControlUserPresence];
This instance also stores and retrieves data in the Secure Enclave, but does not require the user to confirm their presence each time data is retrieved. Instead, the user will be prompted to confirm their presence only on the first data retrieval. A
SinglePromptSecureEnclaveValet instance can be forced to prompt the user on the next data retrieval by calling the instance method
In order for your customers not to receive a prompt that your app does not yet support Face ID, you must set a value for the Privacy - Face ID Usage Description (NSFaceIDUsageDescription) key in your app’s Info.plist.
Migrating Existing Keychain Values into Valet
Already using the Keychain and no longer want to maintain your own Keychain code? We feel you. That’s why we wrote
migrateObjects(matching query: [String : AnyHashable], removeOnCompletion: Bool). This method allows you to migrate all your existing Keychain entries to a Valet instance in one line. Just pass in a Dictionary with the
kSecAttrService, and any other
kSecAttr* attributes you use – we’ll migrate the data for you.
Valet guarantees it will never fail to write to or read from the keychain unless
false. There are only a few cases that can lead to the keychain being inaccessible:
- Using the wrong
Accessibilityfor your use case. Examples of improper use include using
.whenPasscodeSetThisDeviceOnlywhen there is no passcode set on the device, or using
.whenUnlockedwhen running in the background.
- Initializing a Valet with shared access group Valet when the shared access group identifier is not in your entitlements file.
SecureEnclaveValeton an iOS device that doesn't have a Secure Enclave. The Secure Enclave was introduced with the A7 chip, which first appeared in the iPhone 5S, iPad Air, and iPad Mini 2.
- Running your app in DEBUG from Xcode. Xcode sometimes does not properly sign your app, which causes a failure to access keychain due to entitlements. If you run into this issue, just hit Run in Xcode again. This signing issue will not occur in properly signed (not DEBUG) builds.
- Running your app on device or in the simulator with a debugger attached may also cause an entitlements error to be returned when reading from or writing to the keychain. To work around this issue on device, run the app without the debugger attached. After running once without the debugger attached the keychain will usually behave properly for a few runs with the debugger attached before the process needs to be repeated.
- Running your app or unit tests without the application-identifier entitlement. Xcode 8 introduced a requirement that all schemes must be signed with the application-identifier entitlement to access the keychain. To satisfy this requirement when running unit tests, your unit tests must be run inside of a host application.
- Xcode 9.0 or later. Earlier versions of Xcode require Valet version 2.4.2.
- iOS 9 or later.
- tvOS 9 or later.
- watchOS 2 or later.
- macOS 10.11 or later.
Migrating from Valet 2.*
First the good news: you will not have to migrate your keychain data when upgrading from Valet 2.* to Valet 3.*. All Valet objects are backwards compatible with their Valet 2 counterparts. We have exhaustive unit tests to prove it (search for
Now the bad news: the Swift Valet API has slight differences from the Objective-C Valet API. You may have noticed a few of the differences in the sample code above, but here's a rundown of the changes that may affect you.
- Initializers have changed in both Swift and Objective-C - both languages use class methods now, which felt more semantically honest (a lot of the time you're not instantiating a new Valet, you're re-accessing one you've already created). See example usage above.
VALSynchronizableValet(which allowed keychains to be synced to iCloud) has been replaced by a
+[VALValet iCloudValetWithIdentifier:accessibility:]in Objective-C). See examples above.
set(object:forKey:)in Swift. The Objective-C API
-setObject:forKey:remains the same.
set(string:forKey:)in Swift. The Objective-C API
-setString:forKey:remains the same.
SinglePromptSecureEnclaveValetdata retrieval methods now return a single enum SecureEnclave.Result rather than using an
inoutboolean to signal whether a user cancelled. The Objective-C API remains the same.
migrateObjects(from:)now both return a nonnull MigrationResult.
VALAccessControlhas been renamed to
VALSecureEnclaveAccessControlin Objective-C). This enum no longer references
TouchID; instead it refers to unlocking with
biometricdue to the introduction of Face ID.
SinglePromptSecureEnclaveValetare no longer in the same inheritance tree. All three now inherit directly from
NSObjectand use composition to share code. If you were relying on the subclass hierarchy before, 1) that might be a code smell 2) consider declaring a protocol for the shared behavior you were expecting to make your migration to Valet 3 easier.
We’re glad you’re interested in Valet, and we’d love to see where you take it. Please read our contributing guidelines prior to submitting a Pull Request.
Thanks, and please do take it for a joyride!
Help us keep the lights on
3.2.3 - Jan 9, 2019
- Fixes Valet triggering a spurious
'init' is inaccessible due to 'private' protection levelbuild error when a
privateValet initializer is used by a consuming application.
3.2.2 - Oct 3, 2018
- Enforce that migration specifies kSecClassGenericPassword to avoid data loss
3.2.1 - Oct 2, 2018
- A Carthage-only patch release to re-enable usage of Carthage with Valet.
3.2.0 - Oct 2, 2018
- Added support for watchOS
3.1.6 - Aug 28, 2018
- Fixes Xcode 10 warnings about overriding