Cisco AnyConnect (now officially branded as Cisco Secure Client) is standard remote-access software for enterprise networks. However, users often encounter a confusing roadblock when their company credentials expire or require an update: there is no obvious “Change Password” button in the client interface.
Whether you are facing an unexpected password expiration prompt, logging in through enterprise Single Sign-On (SSO), dealing with stuck cached credentials, or configuring your gateway as a network administrator, managing credentials requires understanding how the client interacts with authentication backends. The following guide covers everything you need to update, reset, and troubleshoot your Cisco AnyConnect password.
Table of Contents
Why Is There No Option to Change Password in Cisco AnyConnect?
Many users open the Cisco AnyConnect settings menu expecting an ad-hoc “Change Password” button, only to find connection statistics, diagnostic tools, and profile configurations. This absence is intentional and rooted in the software’s architecture.
Cisco AnyConnect Does Not Store or Manage Accounts
AnyConnect is an access client, not an identity provider. It does not maintain an internal database of user credentials. Instead, it forwards your credentials to an upstream authentication gateway—such as a Cisco Adaptive Security Appliance (ASA), Secure Firewall Threat Defense (FTD), or Cisco Identity Services Engine (ISE). That gateway validates your username and password against a corporate directory service:
* Active Directory (AD) via LDAP or Kerberos
* RADIUS servers using MS-CHAPv2
* Cloud Identity Providers (IdPs) via SAML 2.0 (e.g., Microsoft Entra ID, Okta, PingFederate)
Why Arbitrary Changes Are Blocked
Because AnyConnect does not own your identity profile, it cannot arbitrarily accept a password change request outside of an active authentication negotiation. An ad-hoc password modification can only happen under two conditions:
1. Triggered Expiration: The backend directory flags your account as expired during a login attempt and sends a challenge back through the gateway, causing AnyConnect to render a password-change dialogue box.
2. External Modification: You change your password directly in your enterprise identity provider (such as an internal Active Directory portal or SSO dashboard), after which AnyConnect accepts the new credential on your next connection attempt.
How to Change an Expired Password During AnyConnect Login
If your organization has enabled backend password expiration notifications, AnyConnect will automatically prompt you to update your credentials when they expire or enter the configured warning window.
Follow these steps to submit your updated credentials directly through the client interface:
- Initiate the Connection
Launch Cisco AnyConnect / Cisco Secure Client, select your organization’s VPN connection profile from the drop-down menu, and click Connect. - Submit Expired Credentials
Enter your existing username and current (expired) password, then click OK. - Locate the Password Expiration Prompt
If the VPN gateway recognizes that your password has expired, an inline dialogue appears stating: “Your password has expired. Please enter a new password.” - Input the New Credentials
The dialogue displays three credential fields: - Old / Current Password: Re-enter the expired password.
- New Password: Enter your new credential, ensuring it adheres to your organization’s length and complexity requirements.
- Confirm New Password: Retype the new password exactly as entered above.
- Complete the Handshake
Click OK or Submit. The client securely relays the update to the directory service. Once accepted, AnyConnect finalizes tunnel negotiation, applies security posture checks, and establishes the VPN session.
Updating Cisco AnyConnect Passwords with Modern SAML SSO (Microsoft Entra ID or Okta)
Modern enterprise deployments frequently delegate authentication away from legacy LDAP/RADIUS to cloud-based Single Sign-On (SSO) using SAML 2.0. If your AnyConnect connection launches an embedded browser window or redirects you to a browser tab for Microsoft Entra ID (formerly Azure AD) or Okta, the password update process occurs outside of the standard AnyConnect dialogue.
To change your password in an SSO-driven environment:
- Do Not Rely on the AnyConnect Input Form
Because authentication is decoupled from the AnyConnect client binary, you cannot change an expired SSO password directly through a standard client prompt unless the IdP web view specifically provides a self-service reset link. - Access Your Organization’s Identity Portal
Open a standard web browser and navigate to your identity provider’s self-service portal: - Microsoft Entra ID / Microsoft 365: Visit myaccount.microsoft.com or passwordreset.microsoftonline.com.
- Okta: Navigate to your organization’s subdomain (e.g.,
company.okta.com) and select Settings > Security > Change Password. - Perform the Password Reset
Authenticate using multi-factor authentication (MFA) via Microsoft Authenticator, Okta Verify, or a FIDO2 hardware key, and set your new password. - Reconnect Cisco AnyConnect
Return to Cisco AnyConnect and click Connect. When the SSO authentication window appears, enter your newly updated enterprise password and approve the MFA challenge to complete the connection.
How to Clear Stale or Saved Passwords in Cisco AnyConnect
If you changed your corporate password on another machine or through an external portal, AnyConnect may attempt to auto-fill an old, cached password. This often results in repeated login rejections or account lockouts. Clearing the local cache forces the client to prompt for fresh credentials.
On Windows
- Clear Windows Credential Manager:
- Press
Windows Key + R, typecontrol keymgr.dll, and press Enter. - Select Windows Credentials.
- Under Generic Credentials, look for entries labeled with
Cisco AnyConnect, your VPN gateway URL, orCisco Secure Client. - Click the drop-down arrow next to the entry and select Remove.
- Clear AnyConnect User Profile Preferences:
- Close Cisco AnyConnect completely (right-click the tray icon and select Quit).
- Open File Explorer and navigate to:
%LOCALAPPDATA%\Cisco\Cisco Secure Client
(Or%LOCALAPPDATA%\Cisco\Cisco AnyConnect Secure Mobility Clienton older installations). - Open the
preferences.xmlfile with a text editor. - Locate any
<DefaultUser>or<Username>tags storing obsolete values, clear their contents, and save the file. (Alternatively, deletepreferences_global.xmlif present, which forces AnyConnect to regenerate user defaults).
On macOS
- Clear Keychain Access:
- Open Keychain Access via Spotlight (
Cmd + Space> typeKeychain Access). - In the search bar at the top right, search for
AnyConnector your VPN hostname. - Right-click the matching application password entry and select Delete.
- Clear AnyConnect Preferences File:
- Quit Cisco AnyConnect.
- Open Terminal and remove the user preference cache by running:
bash
rm -f ~/.anyconnect - Relaunch the client and reconnect; you will now be presented with an empty username and password prompt.
Troubleshooting “Password Change Failed” Errors
When attempting to change an expired password directly within Cisco AnyConnect, the client may return an error such as “Password change failed,” “Password change rejected by policy,” or “Authentication failed.”
Use the following troubleshooting steps to isolate and resolve the issue:
- Verify Minimum Password Age Policies
Active Directory often enforces a Minimum Password Age policy (e.g., 1 day) to prevent users from rapidly cycling through old passwords to return to their favorite one. If your password was changed recently, Active Directory will reject another update until the minimum age threshold expires. - Check Complexity and History Requirements
Domain policies generally require passwords to meet specific criteria: - Minimum length (often 12 to 16 characters).
- At least three character classes (uppercase, lowercase, numbers, special symbols).
- Strict non-repetition rules (e.g., must not match the last 10–24 passwords used).
Ensure the new password submitted in the AnyConnect dialogue meets every parameter enforced by your company’s Group Policy Objects (GPOs). - Verify Account Lockout Status
Multiple failed password change attempts may trigger an automated account lockout. Contact your internal IT help desk to check if your account is locked in Active Directory or Azure AD. - Identify Gateway Communication Failures
If the gateway cannot reach the domain controller over a secure communication channel, the password change will fail silently or display a generic error. If basic authentication works with non-expired accounts but password changes fail for all expired accounts, the issue resides on the gateway configuration, not the user client.
Cisco ASA and ISE Password Management Configuration (Administrator Reference)
For network administrators, enabling end-user password resets within AnyConnect requires specific configuration on the headend gateway (Cisco ASA, FTD, or Cisco ISE). Active Directory strictly prohibits password modifications over unencrypted LDAP (port 389); all password-change traffic must use secure protocols.
1. Cisco ASA Password Management over RADIUS (MS-CHAPv2)
To allow password changes using RADIUS, the authentication server must use MS-CHAPv2, as PAP does not support password expiration mechanisms.
aaa-server RADIUS-GROUP protocol radius
aaa-server RADIUS-GROUP (inside) host 10.1.1.50
key cisco123
authentication-port 1812
accounting-port 1813
tunnel-group VPN-REMOTE-ACCESS general-attributes
authentication-server-group RADIUS-GROUP
password-management
The password-management directive instructs the ASA to interact with MS-CHAPv2 password-change challenges and pass them to the AnyConnect client. To provide advance expiration warnings to users, append the notification window:
tunnel-group VPN-REMOTE-ACCESS general-attributes
password-management password-expire-in-days 14
2. Cisco ASA Password Management over Secure LDAP (LDAPS)
If using direct LDAP authentication instead of RADIUS, the connection to Active Directory must be encrypted via SSL/TLS on port 636. Plaintext LDAP password change requests are rejected by default on modern Windows Server domain controllers.
aaa-server LDAP-CORP protocol ldap
aaa-server LDAP-CORP (inside) host 10.1.1.60
server-port 636
ldap-over-ssl enable
ldap-base-dn DC=corp,DC=internal
ldap-scope subtree
ldap-naming-attribute sAMAccountName
ldap-login-dn CN=svc-vpn,OU=Services,DC=corp,DC=internal
ldap-login-password cisco_secure_password
server-type microsoft
tunnel-group VPN-REMOTE-ACCESS general-attributes
authentication-server-group LDAP-CORP
password-management
3. Cisco ISE Settings
When Cisco ISE handles AAA for AnyConnect:
* Navigate to Administration > Identity Management > External Identity Sources > Active Directory.
* Select the targeted Active Directory domain and click the Advanced Settings tab.
* Check Allow user to change password before it expires and/or Allow user to change password when expired.
* Ensure the Identity Source Sequence used in the AnyConnect Authentication Policy includes this Active Directory join point with password management allowed.
Conclusion
Cisco AnyConnect does not provide an independent, on-demand “Change Password” setting because credential authority resides strictly within external directories such as Active Directory, RADIUS, or cloud SSO platforms. If your password has expired under an LDAP or RADIUS setup, AnyConnect handles the update through an automated login prompt. In SAML SSO environments, you must reset credentials through your identity provider’s online portal. When encountering sync issues, clearing cached credentials from your local operating system or verifying domain complexity policies will quickly restore secure VPN access.











Comments