Page History

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 

The EMA uses the common Local Cert store of the 

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

Enter the following URL in the browser to access the

https://<hostname>

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

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 

list of supported browsers and client platforms

for accessing EMA.

Procedure

To log into the Embedded Management Application (EMA):

1. Launch your web browser.

2. Enter the

   Spacevars
   0 product

   EMA URL <ip address/device

1. name> 

   Info

1. title

1. Note

1. When using Internet Explorer/Mozilla Firefox browser, a website security issue may prevent you from going directly to

1. the SBC application login screen, as shown in example below.

   Caption
   0 Figure 1 Certificate Security Error

1. Image Added

2. Click Advanced.

   Caption
   0 Figure 1 Firefox Message - Self-Certified Website
   Image Added

3. Click Add Exception. 

   Caption
   0 Figure 1 Firefox Message - Add Security Exception
   Image Added

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

1. . 

   Caption
   0 Figure 1 Login
   Image Modified

2. Enter your Username

1.  and Password. Your

1. username and

1. password will be supplied along with

1. the 

   Spacevars
   0 product

1.  installation package. Once you have successfully logged

1. into the SBC,

1. your temporary password expires and you are prompted to change your 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.

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.