How to check the configured Password in Call web service smart service?

Hi ,

 

We have some web service invocations implemented to call some other systems

Recently target systems had modified the WSDL endpoints  and password.

We have modified in all the impacted places , but some how latest configured password is not working .

When I tried to call WS from expression rule with the new details its working fine , but not in the existing model activities.

Is there a way to check the password at backend i.e. Appian object DB ?

 

Thanks

Soujanya

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    Hi  you can follow below mention steps to get the configured password:

    1. Highlight and Select the password

    2. Right click and click on inspect elements

    3. Within generated html code, change <input type="password"/> to  <input type="text"/>

    4. Now you can find your password shown in the same box of smart Service.

    But just a quick hint on the issue which you are facing, if you feel that the smart service is still using the old configurations, them delete this smart service and reconfigure the smart service and click on save and publish.

    Also you should look into HTTP Error message, so that you can come to a conclusion whether it's the issue of password or something else.

    Hope this will help you .

  • Thanks for the response.
    As per the http error message(unauthorized user) , its a password issue and after 3 attempts , user gets locked.
    And coming to your other question , these services has been configured in several process models and I don't think deleting and reconfiguring the smart service is not the best way .
  • 0
    Certified Lead Developer
    in reply to Soujanya B
    If you talk about integration, then there should be some base pattern which should be inherited by all the Appian objects.

    For example, username, password, even your process model which contains web service integration.

    It's never a best practice to implement the services at multiple places because this increases the chances of heavy maintenance issue. But if it's a common/base pattern then one changes can be effected to all the places. It's obvious when you depend upon a 3rd party system, they might change their details such as authentication details or the way to authenticate the request, so your system should be designed in such a way so that it can opt for the changes easily.
Reply
  • 0
    Certified Lead Developer
    in reply to Soujanya B
    If you talk about integration, then there should be some base pattern which should be inherited by all the Appian objects.

    For example, username, password, even your process model which contains web service integration.

    It's never a best practice to implement the services at multiple places because this increases the chances of heavy maintenance issue. But if it's a common/base pattern then one changes can be effected to all the places. It's obvious when you depend upon a 3rd party system, they might change their details such as authentication details or the way to authenticate the request, so your system should be designed in such a way so that it can opt for the changes easily.
Children
No Data