11.0

Chapter 6: Configuring and using the Roaming feature and Roaming User Profiles
Setting up HTTPConnection: HTTP
Settings
You use the HTTP Settings dialog box to define and configure the connection to your
web(HTTP)server. Enter information about your connection in the following sections and text
boxes of the dialog box:
Authentication
Passwords
Defines how a user that uses a Roaming User Profile enters the server username and password.
This username/password is to the server, not a local login:
n Prompt for User and Password : Select if local users will be prompted for a
username/password when they connect to the HTTP server.
n User/password : Sets the default username/password needed to connect to the HTTP server.
Be sure to put the domain name followed by a backslash in front of the user login name; for
example, Nuance\JWyman.
Authentication Type
Sets the type of authentication used on the HTTP server you specified as the Address in the
Roaming User Network Location dialog box. Select the type that indicates how your server is
configured:
n Basic : Choose if the server is configured for Basic authentication, where the username and
password are passed over the network as clear text
n Digest : Choose if the server is configured for Digest authentication, where the passwords are
never transmitted across the internet in unencrypted form. Digest is not supported for IIS.
Note: Digest authentication through a proxy server with Internet Information Server (IIS) 6.0 is
not supported.
Note: For security reasons, be sure that anonymous logins are disabled on the HTTP or
HTTPSserver.
Connection
Follow Redirects
If you are storing the Master Roaming User Profiles on a server that redirects incoming con-
nections to another location, you can define how Dragon handles these redirects:
n Never : redirects are never followed, but ignored.
n Always : redirects are always followed.
n Same Scheme Only : only redirects using the same scheme as the client request are permitted.
Keep Connection Alive
This setting tells the client and server to keep the connection alive after the current session ends.
219