Using Credential Store Framework when communicating with Oracle Human Workflow API by Sven Bernhardt
By JuergenKress on Mar 27, 2014
For connecting to Oracle Human Workflow Engine via the provided client API, username and password of an admin user are needed. These credentials could also be useful during task processing, when actions on a task has to be performed on behalf of a user, for example in case of holidays or illness. But how can to manage the admin users credentials in secure way, independent from the target environment?
A first approach is to use a mechanism where the credentials were provided as context parameters in the web.xml, of a Facade Web Service in front of the client API to hide complexity and to force upgrade protection in case of API changes. When deploying this Web Service facade, the parameters are replaced using a deployment plan. This solution works, but has the disadvantage that username and password of the admin user are contained in the deployment plan as clear text. From a SysOps perspective this mechanism is not appropriate.
another possibility must be found to manage user credentials in a
consistent and secure way. An approach to ensure the secure management
of credentials is to use the Oracle Credential Store Framework (CSF),
provided by Oracle Platform Security Services (OPSS). Configuring and
using CSF is quite simple and done in a few steps: Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.