ACS Password Guardian vs Alternatives: Which Is Best for Your Team?

Troubleshooting Common ACS Password Guardian Issues and Fixes

Below are common problems users encounter with ACS Password Guardian and step-by-step fixes you can apply. Follow the ordered steps; try the simplest solution first and move to the next if the issue persists.

1. I can’t sign in

• Check credentials: Verify email/username and password; ensure Caps Lock is off.
• Reset password: Use the Forgot Password flow and follow the emailed reset link.
• Account locked: Wait the lockout period (or contact your admin) if multiple failed attempts triggered a lock.
• SAML/SSO issues: If you use SSO, confirm your identity provider (IdP) session is active and the IdP metadata (certificate, endpoints) hasn’t expired.
• Network/endpoint blocks: Try signing in from a different network or device; check firewall or VPN rules that might block authentication endpoints.

2. MFA (multi-factor) not working

• Time sync for TOTP apps: Ensure your authenticator app’s time is correct (enable automatic time sync on the device).
• Lost device: Use backup codes or the recovery process provided by your org (contact admin if required).
• Push notifications not received: Check network connectivity and app notification permissions; restart the device and the app.
• Hardware token issues: Verify token batteries and that the token is within validity; re-enroll if necessary.

3. Vault items not syncing between devices

• Connection check: Confirm all devices have internet access.
• App version parity: Update ACS Password Guardian to the latest version on each device.
• Force sync/restart: Manually trigger a sync if available; otherwise restart the app and device.
• Conflict resolution: Look for duplicate or conflicting entries; resolve locally then force sync.
• Server status: Check service status (your org’s status page or admin console) for outages.

4. Unable to add or retrieve credentials

• Permission review: Ensure your account has rights to create/view entries in the relevant vault/folder.
• Entry limits or policies: Check for organizational policies that limit credential creation or require approval.
• Field validation errors: Confirm required fields are filled and any password policy rules are met.
• Browser extension issues: If using a browser extension, clear cache, disable conflicting extensions, or reinstall the extension.

5. Browser extension autofill failures

• Extension enabled & up to date: Confirm the extension is enabled and updated.
• Site matching: Confirm the saved credential’s URL exactly matches the site (subdomain, HTTPS).
• Permissions: Ensure the extension has the necessary site access and can run in incognito if needed.
• Form structure changes: Some sites change form fields — try manual copy-paste or re-save the credential.
• Browser compatibility: Test in a different browser to isolate the problem.

6. Slow performance or high memory use

• Update software: Run the latest client and extension versions.
• Reduce item load: Archive or remove unused entries to reduce sync and local storage load.
• Local cache reset: Clear local cache or reinstall the client to reset corrupted caches.
• System resources: Close unnecessary apps, and check for OS-level memory issues.

7. Backup and restore problems

• Verify backup validity: Confirm backups complete successfully and are not corrupted.
• Correct restore file/version: Use the latest compatible backup file for restore.
• Permissions during restore: Run restore with appropriate account privileges.
• Encryption keys: Ensure you have the correct master password or key required to decrypt the backup.

8. Integration or API errors

• API keys & secrets: Confirm API credentials are valid and not expired.
• Rate limits: Check for throttling or rate-limit responses and add retry logic.
• Schema changes: Verify your integration uses the current API endpoints and payload formats.
• Network connectivity & certificates: Ensure TLS certificates are valid and endpoints reachable.

9. Audit logs missing or incomplete

• Log retention & filters: Confirm retention settings and that filters/time ranges aren’t excluding entries.
• Permissions: Ensure you have audit-viewing privileges.
• Collector/service status: Verify the logging service or collector is running and not failing to forward logs.

10. Unexpected access denials

• Role/policy checks: Review role assignments, vault-level policies, and conditional access rules.
• Time-based policies: Check for time-of-day or network-based access restrictions.
• Device compliance: Ensure the device meets any compliance checks (managed device, OS version).

When to contact support or your admin

• After trying steps above with no resolution.
• For account locks that require admin reset.
• For SSO/SAML IdP certificate renewals or tenant-level configuration issues.
• For suspected data corruption or security incidents.

Before contacting support, collect:

1. Exact error messages/screenshots.
2. Steps to reproduce.
3. Affected user(s) and timestamps.
4. Client version(s) and OS/browser.

Quick checklist (try in order)

1. Verify credentials and network.
2. Update client/extension and device OS.
3. Force sync or restart app/device.
4. Check permissions, policies, and audit logs.
5. Collect diagnostic info and contact admin/support.

If you want, I can convert this into a printable troubleshooting checklist, a support-ready report template, or provide step-by-step commands for diagnosing issues on Windows/macOS/Linux — tell me which.