Cisco Unified MeetingPlace, Release 7.0 -- How to Configure HTTP Basic Authentication (Domain)

From DocWiki

Jump to: navigation, search

Main page: Cisco Unified MeetingPlace, Release 7.0

Up one level: Configuration

The HTTP basic authentication method is a widely used industry-standard method for collecting user ID and password information. It works as follows:

  1. Users are prompted by a pop-up login window that is rendered by their web browser.
  2. Users enter valid domain user IDs and passwords.
    Cisco Unified MeetingPlace profile passwords are ignored and not used in the authentication operation.
  3. If the Web Servers accept the login credentials and the user IDs also exist in Cisco Unified MeetingPlace profile databases, users are logged in automatically to Cisco Unified MeetingPlace and are granted access to the Cisco Unified MeetingPlace home page.

Note: The Cisco Unified MeetingPlace profile user ID must match the domain user ID of the user.

The advantage of HTTP Basic Authentication is that it is part of the HTTP specification and is supported by most browsers. The disadvantage is that the password is Base 64-encoded before being sent over the network. Since Base64 is not a true encryption, it can be easily deciphered. You can mitigate this security risk by implementing Secure Socket Layer (SSL) on the Web Server.


Configuring HTTP Basic Authentication (Domain)

Before You Begin

Read Restrictions: User Authentication and Load Balancing.

  1. Sign in to the end-user web interface.
  2. Click Admin.
  3. Click Web Server.
  4. Click the name of the Web Server that you want to configure in the "View" section of the page.
  5. Scroll down to the Web Authentication section.
  6. Select HTTP Basic Authentication (Domain) for "Step 1: Directory."
    "Step 2: Login Method" is automatically set to HTTP Basic Authentication and cannot be changed.
  7. Enter your default logon domain in the field provided.
  8. Select how you want user names transformed for "Username Conversion Function."
    Selecting None applies no transformation to the original user ID string.
  9. Click Submit and wait five minutes for the new configuration to take effect.

What to Do Next

(Optional) Proceed to Verifying the HTTP Basic Authentication (Domain) Configuration.

Verifying the HTTP Basic Authentication (Domain) Configuration

Use a Cisco Unified MeetingPlace end-user profile when completing this procedure.

Before You Begin

Complete Configuring HTTP Basic Authentication (Domain).

  1. Open a web browser and navigate to Cisco Unified MeetingPlace.
  2. Verify the following end-user behaviors:
    • You see an Enter Network Password dialog when accessing the home page.
    • If you have a local account on the Windows server and a matching profile user ID, you are authenticated to Cisco Unified MeetingPlace when you enter your domain user ID and password.
    • If you have a Cisco Unified MeetingPlace profile, your name displays on the Welcome page as firstname, lastname and the Sign In link no longer displays.
    • You can only log in to Cisco Unified MeetingPlace if you are authenticated by the Cisco Unified MeetingPlace Web Server.
    • In IIS, the MPWeb/Scripts folder is set to Basic Authentication.

Rating: 0.0/5 (0 votes cast)

Personal tools