SSH AFX test connector settings fails with 'Request timed out' and a 'Kerberos username' warning in RSA Identity Governance & Lifecycle
Originally Published: 2017-02-10
Article Number
Applies To
RSA Version/Condition: All
Issue
Failed connector settings test. Request timed out.
The AFX mule log file, $AFX_HOME/esb/logs/mule_ee.log, has the following warnings:
[Mule.app.deployer.monitor.1.thread.1] org.mule.module.launcher.DeploymentService:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Started app 'AFX-SETTINGS-Linux' +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Kerberos username [oracle]: WARNING -
System.in has been disabled by the wrapper.disable_console_input property. Calls will block indefinitely.
Kerberos username [oracle]: WARNING -
System.in has been disabled by the wrapper.disable_console_input property. Calls will block indefinitely.
Kerberos username [oracle]: WARNING -
System.in has been disabled by the wrapper.disable_console_input property. Calls will block indefinitely.
No other log files report any errors or information related to this failure.
Running sshd with the -ddd debug option contains a message similar to:
$ /usr/sbin/sshd -ddd Postponed gssapi-with-mic for root from 100.44.55.11 port 41414 ssh2
Cause
- Kerberos is a computer network authentication protocol that works on the basis of tickets to allow nodes communicating over a non-secure network to prove their identity to one another in a secure manner. (Reference taken from Wikipedia.com).
- Generic Security Service Application Program Interface (GSSAPI) is an IETF standard for doing strong encrypted authentication in network based applications. OpenSSH uses this API and the underlying Kerberos 5 code to provide an alternative means of authentication other than ssh_keys. (Information taken from Using GSSAPI authentication at SLAC).
Resolution
Disable Kerberos and/or GSSAPI
Disable Kerberos and or GSSAPI by editing /etc/ssh/sshd_config.
- Login as root.
- Open /etc/ssh/sshd_config in a text editor and and modify the following entries:
- Under Kerberos options, modify any entry that is uncommented and set to yes to no. For example,
From:
# Kerberos options KerberosAuthentication yes
To:
# Kerberos options KerberosAuthentication no
- Under GSSAPI options, set GSSAPIAuthentication and GSSAPICleanupCredentials to no. For example,
# GSSAPI options GSSAPIAuthentication no GSSAPICleanupCredentials no
- Save the file and restart sshd using the following command:
# service sshd restart
Notes
Related Articles
PAN-OS - SAML Relying Party Configuration - RSA Ready Implementation Guide 7Number of Views Enabling debug output for SMTP output action 38Number of Views Admin user always redirected to Access Manager login page 12Number of Views Troubleshooting X-Windows for SecurID protection 6Number of Views RCM API unable to connect to the RCM to get certificate information 7Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?