Hi @TatKhandM ,

Passwords as well as Application parameters are encrypted at FSM server side. 

What is the requirement?

Thank you, 

Ruben

My requirement is need to create a password script to test the performance of the application, The password stored in the DB is encrypted password which is completely different from the password that is been observed from IFS FSM client UI  through any browser tool. 

So which type of encryption logic is used for password at client UI Level ?

Hi @TatKhandM , 

If you want to authorize messages as part of a volume \ performance test you can provide the person_id and password unencrypted in the authentication

<perform_login>
  <authentication>
    <logon_info>
      <person_id>RUMANL</person_id>
      <password>PASSWORDUNENCRYPTED</password>
      <ignore_password_expiry_check>true</ignore_password_expiry_check>
    </logon_info>
  </authentication>
</perform_login>

You don’t necessarily have to create a session though. you can also add the authentication block to the individual transactions (unencrypted ) like this:

<hierarchy_select>
  <authentication>
    <logon_info>
      <person_id>RUMANL</person_id>
      <password>PASSWORDUNENCRYPTED</password>
    </logon_info>
  </authentication>
  <primary_table>request</primary_table>
  <attrs>
    <attr>request.*</attr>
  </attrs>
  <from>
    <table>request</table>
  </from>
  <where>
    <data_constraint>
      <constraint>
        <left_operand>request.request_id</left_operand>
        <operator>eq</operator>
        <right_operand>640</right_operand>
      </constraint>
    </data_constraint>
  </where>
</hierarchy_select>

-Ruben