We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kSecAttrAccessGroup
Apple keychains can share access to keychain items among a collection of apps:
https://developer.apple.com/documentation/security/keychain_services/keychain_items/sharing_access_to_keychain_items_among_a_collection_of_apps/
We'd like to provide this feature across our apps.
Providing the flexibility to specify the shared keychain group or injecting our own keychain storage variant.
Appears currently the KeychainStorageFactory is a concrete internal type which provides the SecItemCopyMatching search query.
KeychainStorageFactory
SecItemCopyMatching
Alternative is to persist our own shared keychain group storing the token & secret in which we provide to GigyaCore on launch.
token
secret
GigyaCore
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Checklist
Describe the problem you'd like to have solved.
Apple keychains can share access to keychain items among a collection of apps:
https://developer.apple.com/documentation/security/keychain_services/keychain_items/sharing_access_to_keychain_items_among_a_collection_of_apps/
We'd like to provide this feature across our apps.
Describe the ideal solution.
Providing the flexibility to specify the shared keychain group or injecting our own keychain storage variant.
Appears currently the
KeychainStorageFactory
is a concrete internal type which provides theSecItemCopyMatching
search query.Alternatives or workarounds
Alternative is to persist our own shared keychain group storing the
token
&secret
in which we provide toGigyaCore
on launch.The text was updated successfully, but these errors were encountered: