You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

In this section:

 

 

HTTPS Support

The EMA GUI is available via TLS-secured (https) access either directly through port 443 or indirectly through port 80 to 443. ACL rules are not applicable to prevent unsecured (http) access.

A sample X.509 certificate, which is a copy of the BMC and the EMA Platform Mode certificate, is shipped along with the 

Unable to show "metadata-from": No such page "_space_variables"
shipment. The size of this certificate is 2,000 bytes.

Note

The BMC is not applicable to

Unable to show "metadata-from": No such page "_space_variables"
.

The EMA uses the common Local Cert store of the 

Unable to show "metadata-from": No such page "_space_variables"
(used also for SIP/TLS) rather than having its own separate certificate store. The operator may replace that sample certificate at any time. The replacement mechanism is implemented with post installation/upgrade scripts.

Certificates with RSA keys up to 4,096 bits are supported.

Note

Unable to show "metadata-from": No such page "_space_variables"
recommends using only 2,048 bit certificates with release 3.1 and discourages the use of 4,096 bit certificates in 3.1 due to anticipated upgrade issues with the current software.

Enter the following URL in the browser to access the

Unable to show "metadata-from": No such page "_space_variables"
EMA:

https://<hostname>

where, the <host name> is one of the management IP addresses of the

Unable to show "metadata-from": No such page "_space_variables"
, or the equivalent DNS name. For example, https://10.54.41.8.

The EMA uses a self-signed certificate which may produce a warning message by Internet Explorer and Firefox. These messages may be ignored.

Note

The

Unable to show "metadata-from": No such page "_space_variables"
is delivered with sample self-signed X.509 certificates. Please be aware that even though these sample certificates will allow you to use HTTPS to access the
Unable to show "metadata-from": No such page "_space_variables"
from EMA, BMC and EMA Platform Mode interfaces, using this protocol with the sample certificates is not a truly secure access method. If your organization requires a more secure access, refer to Generating PKI Certificates.

Note

The

Unable to show "metadata-from": No such page "_space_variables"
supports SHA-256 for certificate verification.

Logging In

Supported Browsers and Client Computers

Refer to 

Supported Browsers and Client Computer Requirements
for a listing of supported browsers and client platforms when accessing EMA.

Procedure

Following are the steps to log into the Embedded Management Application (EMA):

  1. Launch your web browser.
  2. Enter the

    Unable to show "metadata-from": No such page "_space_variables"
    EMA URL <ip address/device name>

    Note

    Sometimes, when using Internet Explorer/Mozilla Firefox browser, website security issue may prevent you from going directly to the  SBC application login screen as shown in example below.

    Click Advanced.

    Certificate Security Error

    Click Add Exception.

    Firefox Message - Self-Certified Website

    Uncheck the Permanently store this exception check-box and click Confirm Security Exception.

    Firefox Message - Add Security Exception

     

    The Login window appears as shown below:

    Login

  3. Enter Username and Password. Your Username and the Password will be supplied along with the

    Unable to show "metadata-from": No such page "_space_variables"
    installation package. Once you have successfully logged in to SBC, you temporary password expires and you are prompted to change your password.

    Note

    This change password screen appears only for the first log on of the new user.

    Change Password


    Ensure the following criteria are met to successfully change the password:

    • Minimum length of characters is 8.
    • Minimum number of upper case characters is 1.
    • Minimum number of lower case characters is 1.
    • Minimum number of numeric digits is 1.
    • Minimum number of special characters is 1.
    • Maximum number of consecutive repeating characters is 3.
    • Minimum number of differences compared to the old password is 4.
    • Do not repeat any of the last 4 passwords.
  4. Once the password is successfully changed, enter the Username and the new Password and click Log In.

Incorrect Username-Password Combination

If you enter incorrect Username-Password combination, the following error message is displayed:

EMA Incorrect Login Credentials

 

Information in the Login Window

The Login window displays the following:

  • Username
  • Password

The following table describes the login window components.

Login Window Components

Attributes

Description

Username

Name of the user logging into the application.

Password

Password associated with the user who is logging in.

Note
  • You can also change the password in EMA without logging in to the application. The option to change password is available on the SBC Application login screen.
  • The Username and Password is same as that for the CLI.

 

Messages After Successful Login

After you log on to the EMA, you may get one of the following messages:

  • If you enter the correct login credentials:

    Successful EMA Login

  • If you make mistake, or someone had tried to unsuccessfully log on using your username but gave the wrong password:

    EMA Login Message - Previous Unsuccessful Message

Last Login Display Date

The last login date of the user is displayed during the login time. When a user logs into the CLI/EMA, his/her last successful and failed login date and the IP address is displayed. The user evaluates this information to check illegal activities in the account.The information which are displayed at login:

  1. Last successful login date and time.
  2. Last successful login IP address.
  3. Last unsuccessful login date and time.
  4. Last unsuccessful login IP address.
  5. Number of failed attempts after successful login.

     

Note

Items 3, 4 and 5 display only when the last successful login date is older than the last unsuccessful login date. See the figure Login Message - Previous Unsuccessful Attempts. 

Note

The Last Login Information also displays for a new user for the first login. The new user is first authenticated and then allowed to change the system generated password. 

 

Configuring Banner in Login Screen

  1. On the main screen, navigate to Admin > Application Management. Click Banner chiclet on the left hand side of the page to display the Configure Login Banner window.

  2. Enable Show Login Banner option. You can request the user to acknowledge the Banner by enabling the Require User to Acknowledge Banner before Logging in option and also, you can request the user to acknowledge every time they login or only during the first login.

  3. Add your banner text in the text box next to Banner Text option to display your Banner content.

  4. Click Save to save your edits.

Logging Out of EMA

To log out of the EMA:

  1. Hover the mouse pointer over <your_username> on the menu bar. and click Log Out.

    Log Out

  2. Confirm logging out by clicking Yes on the dialog-box.

    Log Out Confirmation

Security Enhancement to Allow Only One Concurrent EMA Session

This security enhancement is available beginning with SBC Core version 06.02.00R000.

This enhancement enables the EMA application (including EMA in platform mode) to disable concurrent user login sessions. Once a new session is established, any existing session is terminated immediately. When an EMA user attempts to log on, the system validates for any open sessions with the same username. If any existing user session is identified, the user is immediately logged out from the application and allows the new user to log on to the system.

Note

This feature is applicable to all EMA users (local users, radius users, PKI Certificate based users, and CAC users). 


EMA User Logged Out Automatically


  • No labels