Logging Into EMA

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 SBC shipment. The size of this certificate is 2,000 bytes.

The EMA uses the common Local Cert store of the SBC Core (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.

Enter the following URL in the browser to access the SBC EMA:

https://<hostname>

where <host name> is one of the management IP addresses of the SBC, or the equivalent DNS name. For example, https://10.54.41.8.

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

Logging In

Supported Browsers and Client Computers

Refer to 

Procedure

To log into the Embedded Management Application (EMA):

1. Launch your web browser.

2. Enter the SBC EMA URL <ip address/device name> 

   Note

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

   Certificate Security Error

   

3. Click Advanced.

   Firefox Message - Self-Certified Website

   

4. Click Add Exception. 

   Firefox Message - Add Security Exception

   

5. Uncheck the Permanently store this exception check-box and click Confirm Security Exception.  The Login window appears as shown below. 

   Login

   

6. Enter your Username and Password. Your username and password will be supplied along with the SBC installation package. Once you have successfully logged into the SBC, your temporary password expires and you are prompted to change your password.

Change Password

Ensure your new password meets the following criteria:

• • 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.

7. Once your password is successfully changed, enter your username and new password on the Login screen and click Log In.

Last Login Information 

 When a user logs into either the CLI or EMA, information on the last successful and failed login attempts is displayed. The information shown includes:

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.

    

Configuring a Banner in the 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 EMA:

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

Log Out

Security Enhancement to Allow Only One Concurrent EMA Session

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