Server Configuration > Global Development Using a Proxy > Security Considerations for FSA > Authentication
  
Authentication
The Integrity Lifecycle Manager server supports a wide variety of authentication schemes that also apply in an FSA environment. Users must provide valid credentials (user name and password) in order to connect to a server or proxy. For detailed information on authentication, see “Choosing Your Security Policy”.
If a user’s proxy and remote credentials are the same and that user has validated against the remote host, the proxy credential input is ignored.
* 
Proxy-side aliases are case sensitive when matched from the client. FSA does not support Windows Single Sign-On authentication.
FSA does not support client authentication by IP address on the host Integrity Lifecycle Manager server. Authentication by IP address must be set on the proxy.
If you change security realms on a remote server, connecting clients and proxies must be restarted to log in successfully.