any other method instead of using web service
My customer has many managed servers and a sperated server with an application which is for mantain all the server's username and password. Becuase according to company's policy, all the server's password should be changed periodically. And they need to get the latest password when execute OO flow. I suggest the customer to use Web service to get the password then use the password in OO flow if the application provide web service, they said that the application is developed by other vision, it will take a long time to work with the vision. So they want to know beside using web service, is there other way to get the password in OO flow?
Thank you for contacting HPE Forum.
My name is Olman GuzmanI am from the OO/CSA team. Regarding your question, given the scenario you describe on this thread, I believe that the best way to implement what you’re trying to achieve is, by using web services. The point is that we do not know very well the application being used to handle the users and passwords, we don’t even know its limitations or scopes so, a web service would be the best way out of this scenario. Best Regards,
Customer Support Engineer
If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
If this application generates the passwords on the fly, meaning that you have to interact with it in order to get the password, can you invoke that from the HTTP2 operation in OO and parse the response?
You could make use of System Accounts - in which case you anyway need a mechanism to keep those up to date in the Central environment (Central value vs deployed value of the System Accounts) - the good part is that the mechanism can be automated with OO once the enpoints for the scenario are set.
You could make use of sensitive System Properties values of CloudSlang based system properties - in which case you anyway need a mechanism to keep those up to date in the Central environment (Central value vs deployed value of the sensitive System Property) - the good part is that the mechanism can be automated with OO once the enpoints for the scenario are set.
You could use the "web service approach" and rather rely on an external credential mechanism tool, like for instance Vault. You can store and retrieve credentials from VAULT anytime you want with an OO Flow (there is CloudSlang based content for this) - in which case you anyway need a mechanism to keep those credentials up to date in VAULT whenever the user changes credentials - the good part is that the mechanism can be automated with OO once the enpoints for the scenario are set.
I think the nicest one would be the VAULT one aka the web service one as you originally pointed out to the customer.
Hope it helps,