Contents

Popular
Contents

If a User that is used to connect to the LDAP server has read-only permissions, then create 'admin' user and 'administrator' group manually. By default, Fiorano Server tries to create admin/administrator for internal use.

Prerequisite:

Icon

To use a different User other than Admin/Anonymous to create internal server connections, the user credentials have to be changed in all the places where it is being used. Refer to the Editing Server Profile configurations section that follows the section below.

Editing Admin Password

From eStudio

To change the Admin password from eStudio, log on to the Enterprise Server and perform the following actions:

  1. Click the Users node under the Security section.


    Figure 1: List of users under the Users node

  2. From the list of users, right-click the ADMIN user, and click the Change Password option.


    Figure 2: Option to change password

  3. In the Change Password dialog box, provide the new password and click OK.

    Icon

    Old password need not be provided for an Admin user.


    Figure 3: Changing the admin password

Icon

Changing Admin password requires profile changes and server restart as explained in the Editing Server Profile configurations section below.

Icon

Remember the password, because if the password is lost/forgotten, it cannot be recovered! Raising a Support Ticket to reset the security database is the only solution.

From Dashboard

To change the Admin password from the dashboard, log on to the Fiorano Web Console and perform the following actions:

  1. Click the Users node under the Security section.
  2. From the list of users, select the ADMIN user, and click the Change Password option.

  3. In the Change Password dialog box, provide the new password and click OK.


    Figure 4: Changing the admin password in the Dashboard

Icon

Changing Admin password requires profile changes and server restart as explained in the section below.

Editing Server Profile configurations

Administrator user credentials are used for authenticating MQ and JMS server connections. So, if the Admin password is changed from the User Account as explained above, the same needs to be edited in the:

  • FES and FPS Profiles (FES HA and FPS HA in case of HA profile).
  • CPS (Configuration Property Sheet) of those microservices which use Admin user credentials.

Sections below illustrate the configuration steps.

Icon

These steps must also be performed while migrating from an earlier version that consists of modified user accounts such as changing the password for admin and deleting an anonymous user.

FES and FPS profiles

Changes to the FES profile

  1. Load FES profile in eStudio Profile Management perspective.
  2. Stop the FES server.
  3. Navigate to Fiorano > Esb > Transport > FESTransportManager > MQProvider
  4. Change the password corresponding to admin user.


    Figure 5: Providing the new password under the MQProvider properties

  5. Navigate to Fiorano > jmx > engine > ClientJMXEngine.
  6. Change the password corresponding to the admin user.


    Figure 6: Providing the new password under the ClientJMXEngine properties

  7. Save the profiles, start FES and login to Fiorano eStudio with the new password.

Changes to the FPS Profile

The path to the MQ Provider and JMX Client is the same as that of the FES profile above and thereby the steps are similar too; just that here it is done on the peer server profile.

  1. Load FPS profile in eStudio Profile Management perspective.
  2. Stop the FPS server.
  3. Navigate to Fiorano > Esb > Peer > Transport > FPSTransportManager > EnterpriseServer
  4. Change the username and password to use admin user credentials replacing the anonymous user credentials which are present by default.


    Figure 7: Providing the new password under the EnterprseServer properties
     
  5. Navigate to Fiorano > jmx > engine > ClientJMXEngine.
  6. Change the password corresponding to the admin user.


    Figure: 8 Providing the new password under the ClientJMXEngine properties

  7. Save the profile, start FPS and login to Fiorano eStudio with the new password.

FES HA and FPS HA profiles

The path to the MQ Provider and JMX Client is the same as that of the FES/FPS profile above and thereby the steps are similar too; just that here it is done on the HA profile of FES and FPS.

Changes to the FES HA profile

  1. Load FES HA profile in eStudio Profile Management perspective.
  2. Stop the FES server.
  3. Navigate to Fiorano > Esb > Transport > FESTransportManager > MQProvider
  4. Change the password corresponding to admin user.


    Figure 9: Providing the new password under the MQProvider properties

  5. Navigate to Fiorano > jmx > engine > ClientJMXEngine.
  6. Change the password corresponding to the admin user.


    Figure 10: Providing the new password under the ClientJMXEngine properties

  7. Save the profiles, start FES and login to Fiorano eStudio with the new password.

Changes to the FPS HA Profile

  1. Load FPSHA profile in eStudio Profile Management perspective.
  2. Stop the peer server.
  3. Navigate to Fiorano > Esb > Peer > Transport > FPSTransportManager > EnterpriseServer
  4. Change the username and password to use admin user credentials replacing the anonymous user credentials which are present by default.


    Figure 11: Providing the new password under the EnterprseServer properties
     
  5. Navigate to Fiorano > jmx > engine > ClientJMXEngine.
  6. Change the password corresponding to the admin user.


    Figure:12 Providing the new password under the ClientJMXEngine properties

  7. Save the profile, start FPS and login to Fiorano eStudio with the new password.

AGS and AMS profiles

Icon

Refer to the Changing Admin Password section in the API Documentation.

Editing Component configuration

Few microservices use Anonymous user credentials to perform lookups and to create admin connections. These credentials must be changed to reflect the changes to admin/anonymous users if any.

Examples

Stub microservices

  1. Open the Stub CPS (Configuration Property Sheet) and go to FES Connection Configuration.
  2. Under the Component Configuration section in the FES Connection Configuration dialog box, change the username and password accordingly.

  3. Save and Close and run the microservice.

    Icon

    Using the named configuration helps avoid changes in multiple places.


    Figure 13: Connection Configuration properties pertaining to the WSStub microservice

Exception Listener

  1. Open the CPS and go to JNDI details section.
  2. Under the Component Configuration section in the JNDI details dialog box, change the JNDI username and password.


    Figure 14: JNDI Configuration properties pertaining to the ExceptionListener microservice

  3. Go to FES Connection Configuration.
  4. Under the Component Configuration section in the FES Connection Configuration dialog box, change the username and password accordingly.


    Figure 15: Connection Configuration properties pertaining to the ExceptionListener microservice

JMS Components

  1. Open the CPS and go to JNDI Configuration section.
  2. Under the Component Configuration section in the JNDI Configuration dialog box, change the JNDI username and password.


    Figure 16: JNDI Configuration properties pertaining to the JMSIn microservice
Adaptavist ThemeBuilder EngineAtlassian Confluence