Prerequisite

If the 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.

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
   
   

From Dashboard

To change the Admin password from the dashboard, log on to the Fioano 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

Editing configurations after changing Admin Password

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

• FES/FPS Profile.
• CPS (Configuration Property Sheet) of those microservices which use Admin user credentials.

Sections below illustrate the configuration steps.

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.
5. Save the profiles, start FES and login to Fiorano eStudio with the new password.
   
   
   Figure 5: Changes to reflect password change for Admin user

Changes to the Peer 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 6: Changes corresponding to anonymous user deletion in Peer Profile
    
5. Save the profiles, start FPS and login to Fiorano eStudio with the new password.

Changes to the 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 7: 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 8: 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 9: 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 10: JNDI Configuration properties pertaining to the JMSIn microservice