- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Trusted systems - authentication method with QAS
Operating System - HP-UX
1820619
Members
1922
Online
109626
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2010 08:12 PM
01-20-2010 08:12 PM
Trusted systems - authentication method with QAS
Dear all,
Recently we have implemented QAS (Quest Authentication system) integrated with windows AD for identity management for our HP-UX (11.23/11.31) and Linux (RHEL/OEL) servers.
After this, we are unable to use SFTP or SCP with the new Windows AD user-id. It fails with the following error in the sshd.log
“fatal: PAM: pam_setcred(): No account present for user”
One the verbose mode I found that the authentication method invoked is keyboard-interactive and this is the reason for the error. If I continue entering wrong password for three times, fourth time it automatically goes to password.
Below is the verbose output:
scp -v testfile pm.srividhya@dwapps.ad@jmiddb01:/tmp
.
.
.
.
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/identity
debug1: Trying private key: /root/.ssh/id_rsa
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,password,keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,password,keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
pm.srividhya@dwapps.ad@jmiddb01's password:
Is there any way to automatically make the authentication method to be selected as “password” after public key?
Or is there any patch available to fix this?
Regards,
Srividhya
Recently we have implemented QAS (Quest Authentication system) integrated with windows AD for identity management for our HP-UX (11.23/11.31) and Linux (RHEL/OEL) servers.
After this, we are unable to use SFTP or SCP with the new Windows AD user-id. It fails with the following error in the sshd.log
“fatal: PAM: pam_setcred(): No account present for user”
One the verbose mode I found that the authentication method invoked is keyboard-interactive and this is the reason for the error. If I continue entering wrong password for three times, fourth time it automatically goes to password.
Below is the verbose output:
scp -v testfile pm.srividhya@dwapps.ad@jmiddb01:/tmp
.
.
.
.
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/identity
debug1: Trying private key: /root/.ssh/id_rsa
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,password,keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,password,keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
pm.srividhya@dwapps.ad@jmiddb01's password:
Is there any way to automatically make the authentication method to be selected as “password” after public key?
Or is there any patch available to fix this?
Regards,
Srividhya
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2010 08:35 AM
01-21-2010 08:35 AM
Re: Trusted systems - authentication method with QAS
It is your SSH client which is providing the sequence of preferred authentication methods. Look for the ssh_config PreferredAuthentications option on the system from which you're connecting:
PreferredAuthentications
Specifies the order in which the client should try protocol 2 authentication methods. This allows a client to prefer one method (e.g. keyboard-interactive) over another method (e.g. password) The default for this option is: gssapi-with-mic, hostbased, publickey, keyboard-interactive, password.
PreferredAuthentications
Specifies the order in which the client should try protocol 2 authentication methods. This allows a client to prefer one method (e.g. keyboard-interactive) over another method (e.g. password) The default for this option is: gssapi-with-mic, hostbased, publickey, keyboard-interactive, password.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP