AWS wickr documentation change
Summary
Added troubleshooting section for desktop keychain/secure store errors with OS-specific credential protection details.
Security assessment
Documents security feature (OS credential stores) but doesn't address specific vulnerability. Explains how credentials are protected in Windows Credential Manager, macOS Keychain, and Linux Secret Service.
Diff
diff --git a/wickr/latest/userguide/troubleshoot-enduser.md b/wickr/latest/userguide/troubleshoot-enduser.md index af176f73a..60f8e2209 100644 --- a//wickr/latest/userguide/troubleshoot-enduser.md +++ b//wickr/latest/userguide/troubleshoot-enduser.md @@ -7 +7 @@ -Before you beginCommon login issuesRegistration issuesReset your passwordCollect logs for your administrator +Before you beginCommon login issuesRegistration issuesReset your passwordCollect logs for your administratorDesktop keychain or secure store errors @@ -26,0 +27,2 @@ This section helps you troubleshoot common login and registration issues with AW + * Desktop keychain or secure store errors + @@ -207,0 +210,19 @@ If you can't reach the menu – for example, if the issue occurs before sign-in +## Desktop keychain or secure store errors + +Wickr uses your operating system's secure credential store (Credential Manager on Windows, Keychain on macOS, or Secret Service on Linux) to protect your login credentials. If you see errors related to the keychain, secure store, or saved credentials, try the following steps in order. + + 1. **Restart the Wickr client.** Close Wickr completely and reopen it. This resolves most one-time keychain access failures, including "SYSTEM SECURITY DELAY" prompts. + + 2. **Sign out of and back into your operating system.** Log out of your OS user session (not Wickr) and log back in. This resolves issues caused by password changes, OS updates, sleep/wake cycles, or fast user switching. + + 3. **Restart your device.** A full restart clears transient session state that can prevent Wickr from accessing the secure store. + + + + +If the issue persists after all three steps, the problem is with your device's credential store rather than Wickr. Contact your IT team or refer to your platform's documentation. + +###### Note + +If other applications on your device also have trouble accessing saved credentials, the issue is with your operating system's credential store or an enterprise policy — not with Wickr. Contact your IT administrator. + @@ -216 +237 @@ Troubleshoot -Document history +Call issues