Resolving Password Authentication Failure by Changing Service-Type to HTTP
The login repeatedly reported a password error despite correct credentials because the user was configured with service-type web, which requires WEB authentication; changing the service-type to http corrected the issue and allowed successful login.
Problem description
After setting a username and password, the login always reported a password error. The user also changed the password but still received the same error. The user configuration was as follows:
aaalocal-user admin password cipher FN!42&5^N3,,OEA!!local-user admin service-type web telnetlocal-user admin level 3authentication-scheme defaultProcess
1. After adding the following command, the login worked normally: local-user admin service-type http Advice and summary
This issue is minor but easy to mistake. Many people interpret service-type web as a web‑page login, whereas it actually designates a WEB authentication user, not an HTTP login. Changing the service‑type to http resolves the problem.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Practical DevOps Architecture
Hands‑on DevOps operations using Docker, K8s, Jenkins, and Ansible—empowering ops professionals to grow together through sharing, discussion, knowledge consolidation, and continuous improvement.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.