iOS: allow configuring the Keychain accessibility of stored credentials (e.g. afterFirstUnlockThisDeviceOnly)
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 52/100
- Type d'issue
- Fonctionnalité
- Clarté
- Clairement spécifiée
- Activité
- Active
- Stack technique
- ios, typescript
Piste de recherche
Start with ios/NativeBridge.swift and trace how credentialsManagerStorageKey reaches the two SimpleKeychain constructions. Check how the iOS client options are declared and passed through, then inspect the existing credential storage behavior for items saved before a configuration change. Done means an optional iOS accessibility setting reaches both constructions, existing credentials are handled as described, and the default remains .afterFirstUnlock; add or update focused tests and documentation for the recommended setting.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Checklist
- I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
- I have looked into the API documentation and have not found a suitable solution or answer.
- I have searched the issues and have not found a suitable solution or answer.
- I have searched the Auth0 Community forums and have not found a suitable solution or answer.
- I agree to the terms within the Auth0 Code of Conduct.
Describe the problem you'd like to have solved
On iOS, NativeBridge.swift builds the credentials manager with SimpleKeychain(service: key) or the default SimpleKeychain(), with no accessibility argument (lines 71 and 73 on master, unchanged in 5.11.x through 6.2.0). Stored credentials, the refresh token included, therefore get SimpleKeychain's default kSecAttrAccessibleAfterFirstUnlock.
Items in that class move to another device through an encrypted backup restore or Quick Start. React Native apps have no way to choose a …ThisDeviceOnly class. Mobile security assessments (OWASP MASVS-STORAGE) regularly flag a refresh token that isn't bound to the device. Today the only fix is patching ios/NativeBridge.swift.
Describe the ideal solution
An optional, iOS-only client option (for example credentialsManagerKeychainAccessibility, next to credentialsManagerStorageKey), mapped to SimpleKeychain's Accessibility and passed to both SimpleKeychain constructions in NativeBridge.swift. The default stays .afterFirstUnlock, so nothing changes for existing apps.
Two details matter for apps that adopt it:
- Existing installs. SimpleKeychain's
setfalls back toSecItemUpdatewith onlykSecValueDatawhen the item exists, so an item stored before the option was set keeps its old class until the user signs out. Ideally the SDK moves existing items to the configured class in place withSecItemUpdateonkSecAttrAccessible. That is atomic and never signs the user out. (The read query names only service and account, so items stay readable before and after the move.) - Docs. Recommend
.afterFirstUnlockThisDeviceOnlyover.whenUnlocked*, since renewals that run while the device is locked (background tasks, silent pushes) need the item.
Alternatives and current workarounds
- A
patch-package/pnpm patchofios/NativeBridge.swiftthat passesaccessibility: .afterFirstUnlockThisDeviceOnlyand, once at init, runs aSecItemUpdateover thecredentials,dpop_thumbprintandcredentials_session_expiryitems. credentialsManagerStorageKeychanges only the Keychain service, andlocalAuthenticationOptionsadds a biometric prompt. Neither changes the accessibility class.
Additional context
- Checked on 5.11.4, 6.0.0, 6.1.0, 6.2.0 and
master. - Auth0.swift 3.3.0 (
CredentialsManager,storage: CredentialsStorage = SimpleKeychain()) and SimpleKeychain 1.3.0 (accessibility: Accessibility = .afterFirstUnlock) keep the same default. - Android is unaffected:
SecureCredentialsManageralready encrypts with a key held in the Android Keystore. - The DPoP key is already stored
ThisDeviceOnly(SecureEnclaveKeyStore/KeychainKeyStorein Auth0.swift), so this would bring the credentials in line with it.
- Langage dominant
- TypeScript
- Étoiles
- 553
- Forks
- 244
- Merge moyen
- 19 h
- PR mergées (30 j)
- 39
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de auth0/react-native-auth0
-
feature request
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 45/100
auth0/react-native-auth0#1458 · 8 commentaires · 3 réactions ·
Les mainteneurs répondent en général sous 1 jour
-
Users getting logged out with "Unsuccessful Refresh Token exchange, reused refresh token detected"Peut-être pris @subhankarmaiti l’a pris il y a 339 jours. Ouvertebug
auth0/react-native-auth0#1374 · 50 commentaires · 2 réactions · 1 personne assignée ·
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de auth0/react-native-auth0
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
milind-soni/OpenMausBot#6730 ·
Les mainteneurs répondent en général sous 1 jour
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Ouvertearea: @angular/build
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100
angular/angular-cli#34764 ·
Les mainteneurs répondent en général sous 1 jour
-
status/need-triage
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
google-gemini/gemini-cli#30384 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
P2
Difficulté 1/5 Moins d'une heure Accessibilité débutants 84/100
Les mainteneurs répondent en général sous 1 jour
-
area:image documentation good first issue
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
Les mainteneurs répondent en général sous 1 jour