basic authentication

Outlook does not allow you to use Basic authentication when connecting to your RPC proxy server without using SSL encryption.

If you use Basic authentication , we strongly recommend that you use Transport Layer Security ( TLS ) encryption to help improve security .

At least, they really should all implement digest authentication, and stop using (or warn users about) basic authentication.

By itself, Digest authentication is only a small improvement over Basic authentication.

Gets or sets the domain name to be used for basic authentication and digest authentication.

Basic Authentication passes the name and password in clear text, so it is not particularly secure unless run from within SSL.

Yet another alternative is to set up a replica Lotus Domino Document Manager server and to configure it with basic authentication.

The default form of HTTP authentication, "basic authentication, " sends passwords in plain text.

The name of the domain to use for basic authentication and digest authentication.

The following table illustrates some of the differences between Basic authentication and NTLM authentication.

The initial user's name and password is still transmitted in clear text, similar to basic authentication.

Note: Feeds that are designated as private or custom can be accessed using HTTP basic authentication with SSL.

You can use Basic authentication, Integrated Windows authentication, certificate-based authentication, or RSA SecurID.

Basic authentication is supported by all Web browsers, but is not secure unless you require Secure Sockets Layer (SSL) encryption.

Basic Authentication over TLS Select this option to encrypt the transmission of the Basic authentication user name and password.

Basic authentication is one of the two required authentication mechanisms in the HTTP 1. 1 Specification.

Deselect "Allow Anonymous Access" and select "Basic Authentication" . You'll also need to have a username with a password.

IIS authenticates the HTTP request using Basic authentication or NTLM authentication, depending on the Outlook profile setting.

The server sends the serialized credentials, including the sending server's identity for basic authentication, to the target server.

We've once again chosen to use a HTTP Basic authentication header to propagate the identity of the caller to the provider.

Basic authentication is made up of an Authentication header that contains the base64-encoded user name and password separated by a colon.

Basic authentication is simple user name and password authentication. Users are prompted to enter in their user name and password.

If you use Basic authentication, Outlook prompts you for user name and password information.

With Basic authentication, the original caller's credentials are available to the Web application in server variables.

We recommend that you use Basic Authentication and SSL for connections from the Subscriber to IIS.

This parameter specifies whether Basic authentication is enabled on the Outlook Web Access virtual directory.

If you use basic authentication, consider implementing Transport Layer Security (TLS) for more security.

If you specified Basic authentication on the report server virtual directories, choose Basic Authentication.

Basic Authentication: Database Mail uses the username and password specified to authenticate on the SMTP server.

This solution deploys a cluster of WebSEAL instances that are configured for both basic authentication and form-based authentication.

This includes requests under integrated, digest or basic authentication SOAP Batch SQL Requests.

However, if you use Basic authentication, you must type your domain, user name, and password every time that you start an Outlook session.

Basic authentication requires that you provide a user name and password.

It is recommended that you use a separate report server if your security model includes Basic authentication.

You can set the credentials for any Web site that uses basic authentication or Integrated Windows authentication.

The Send connector only performs Basic authentication after the Transport Layer Security (TLS) session has been established.

To require a password if your site is hosted on IIS, you can deselect Allow Anonymous Access and select Basic Authentication.

You cannot turn off forms-based authentication and turn on Basic authentication in a single task.

Basic authentication is not affected by reverse proxying or Web publishing and works regardless of firewalls.

We recommend using Basic Authentication with Web synchronization.

If you are using Basic authentication, a domain account must exist in the Active Directory forest to use for Basic authentication.

Configure HTTP basic authentication for the Web services provider.

If you use Basic authentication, a domain account must exist in each forest to use for Basic authentication.

Configure HTTP basic authentication for the Web services client programmatically.

When you use Basic authentication or Integrated Windows authentication, users are prompted for their logon information only one time.

All access to the appliance is managed with HTTPS basic authentication using user ID and password.

For more information about basic authentication, see Resources.

Set the smart host authentication method to Basic authentication requires TLS.

If the site requires authentication, you must do your own custom form or basic authentication to the other application.

The password to use for basic authentication and digest authentication.

This requires that the server can support NTLM or Basic authentication.

Class when performing basic authentication.

It is recommended that you use FTP with Anonymous or Basic authentication.

Enable only Basic authentication for the Web application.

Indicates the password from a basic authentication attempt.

The dialog assumes that basic authentication is in use.

The client's identity is sent as the user name from the basic authentication.

Select basic authentication for this example.

Basic authentication transmits user names and passwords in clear text.

To select the type of authentication, you must set your Outlook profile to use either Basic authentication or NTLM authentication.

The user name and password for Basic authentication are stored in clear text in the Web. Config file.

Gets or sets the user name to send for basic authentication and digest authentication.

Basic authentication sends credentials in clear text.

Basic authentication sends information in clear text.

You can use Basic authentication in both workgroup and domain deployments.

This problem may occur if you are using a third-party proxy product that uses only basic authentication.

Use basic authentication over Secure Sockets Layer (SSL).

Holds the user name and password from a basic authentication request.

Basic authentication is supported by most browsers.

If you are using Basic authentication over TLS, you must provide the FQDN of the remote Hub Transport server in the smart host settings.

if you provide credentials for basic authentication , they are sent to the server in clear text.

It is not required to provide the user name and password under the Basic Authentication section.

Therefore you need to configure either basic authentication or a combination of basic and token-based authentication.

Password that the Merge Agent uses when connecting to the Web server that is hosting Web synchronization using Basic Authentication.

Indicates that basic authentication should be used on the connection.

Basic authentication sends the user name and password in clear text.

Select this option when the smart host requires Basic authentication.

You can also use basic authentication (a user name and password) to authenticate yourself to the SMTP server.

Basic authentication sends the user's user name and password in clear text.

Login that the Merge Agent uses when connecting to the Web server that is hosting Web synchronization using Basic Authentication.

Figure 4 shows the generated form elements with Basic authentication selected.

If you are using a firewall that does not handle NTLM, you must use Basic authentication over SSL.

The client's identity is sent as the user name (with no password), because basic authentication is used.

The back-end Exchange 2003 server is configured to use only Basic authentication.

Basic authentication is easy to implement, so it is popular for prototypes and situational applications.

If you must access documents from Outlook Web Access, you must use Basic authentication.

We recommend that you configure this Send connector to use Basic authentication plus TLS to authenticate to the legacy Exchange server.

So, now you're sure that you can make an HTTP GET request using Basic authentication and parse the results.

It can recover both Autocomplete and HTTP basic authentication passwords from IE secret store.

When the Client Access server role is installed, the Exchange ActiveSync virtual directory is configured for Basic authentication.

This parameter specifies whether Basic authentication is enabled on the Exchange Web Services virtual directory.

When the Client Access server role is installed, the Exchange ActiveSync virtual directory is configured for Basic authentication.

The Exchange ActiveSync virtual directory is configured to use Basic authentication with SSL.

You don't want to use Basic authentication.

Property is required if the proxy server is configured to use Basic authentication, even if SQL Server Mobile Relay has been configured.

Basic authentication The Exchange 2007 Hub Transport servers and the external SMTP servers authenticate by using Basic authentication.

Microsoft Exchange Server has detected that Basic authentication is being attempted between this server and server %1.

To use Basic authentication, disable Anonymous access for your Web application's virtual root directory and select Basic authentication

HTTP basic authentication is fairly straightforward and only requires you to enter the URL on the basic settings page and select

Establishing Internet Mail Flow Between a Hub Transport Server and a External SMTP Gateway by Using Basic Authentication

Establishing Internet Mail Flow Between a Hub Transport Server and a External SMTP Gateway by Using Basic Authentication

If you will not be using TLS encryption and you want to allow Basic authentication on an unsecured port, run the following command

If you will not be using TLS, but you want to restrict Basic authentication to use only secured ports, run the following command

Authentication of Clients using Basic Authentication

To create a new Send connector and use Basic authentication with TLS to provide only confidentiality, run the following command

Basic authentication over Transport Layer Security (TLS)

If you use Basic authentication, you can select from the following two methods to also use Transport Layer Security (TLS)

To configure cross-forest connectors between Exchange 2007 and Exchange 2003 servers in separate forests and use Basic authentication

Because you are using forms-based authentication and not basic authentication, change the ba-auth from https to none

Basic authentication only after starting TLS

Basic authentication only after starting TLS

How to Verify That RPC Proxy Server Has Basic Authentication Configured

Part 2 of this tutorial builds upon Part 1, showing you how to configure HTTP basic authentication. Here you

If you are using basic authentication, you must create an HttpContext instance