Authenticating client applications built with Flex
There are several ways that LiveCycle User Manager
can authenticate a Remoting request from a Flex application, including
LiveCycle single sign-on through the central login service,
basic authentication, and custom authentication. When neither single
sign-on nor anonymous access is enabled, a Remoting request results
in either basic authentication (the default) or custom authentication.
Basic authentication relies on standard J2EE basic authentication
from the web application container. For basic authentication, an
HTTP 401 error causes a browser challenge. That means that when
you attempt to connect to a LiveCycle application by using
RemoteObject, and have not yet logged in from the Flex application,
the browser prompts you for a user name and password.
For custom authentication, the server sends a fault to the client
to indicate that authentication is required.