SecureTransport 5.4 Administrator Guide Save PDF Selected topic Selected topic and subtopics All content Command line client (FTP, FTPS, HTTPS, and SSH) user authentication Command line clients log on to SecureTransport directly, not through the SSO portal. If the client presents a user name and password or a certificate, SecureTransport first tries to authenticate the user by comparing it to the user profiles defined in SecureTransport. In case SecureTransport cannot authenticate the user, it passes the user name and password to SiteMinder for authentication. If all authentication attempts fail, the user receives an error message and is disconnected. Note The SecureTransport command line client does not work through a Web gateway or proxy (even when using HTTPS). So, SecureTransport Server must be made directly accessible to command line clients. Related topics: Web client (HTTP and HTTPS) user authentication User access control (authorization) Related Links
Command line client (FTP, FTPS, HTTPS, and SSH) user authentication Command line clients log on to SecureTransport directly, not through the SSO portal. If the client presents a user name and password or a certificate, SecureTransport first tries to authenticate the user by comparing it to the user profiles defined in SecureTransport. In case SecureTransport cannot authenticate the user, it passes the user name and password to SiteMinder for authentication. If all authentication attempts fail, the user receives an error message and is disconnected. Note The SecureTransport command line client does not work through a Web gateway or proxy (even when using HTTPS). So, SecureTransport Server must be made directly accessible to command line clients. Related topics: Web client (HTTP and HTTPS) user authentication User access control (authorization)