When content includes resources that are secured by HTTP authentication, EditLive may ask authors to enter their username and password, even if they have already logged in via their browser. Note that this only applies to HTTP authentication, such as basic, digest or NTLM, not cookie or form based authentication. The extra dialog appears because browsers do not allow EditLive to access the username and password the author entered. Form or cookie based authentication works because EditLive can access the cookies set in the browser and send them to the server, maintaining the authentication session.
There are two ways to avoid the authentication dialog appearing:
- Switch from the default HTTP layer to the "sun" connection layer. See the setHttpManagerLayer call. (This is the default in EditLive 9 or newer)
- Specify the login details in the configuration file. This is done in the the authentication element of your configuration file.
In most cases, the best option is to switch to the "sun" connection layer. This layer uses the browser to send requests for other resources so it has access to the author's authentication information. The only drawback of using the "sun" connection layer is that browsing WebDAV servers is not supported. WebDAV connections will always be made with the default HTTP layer.