10-25-2013 10:07 AM
This isn't acceptable. How are we supposed to run headless flows if the user has to type in their password in the middle of a flow run?
Input of the type Credentials: Logged-In User Password
To improve security, the password is no longer automatically transferred when a Credentials input is of the type Logged-In User Password. Instead, the user will be asked to enter the password manually in a prompt message.
10-25-2013 10:51 AM
12-05-2013 06:44 PM
I agree with Don.
How are we supposed to Run headless flows in a User's context?
There are many ways to get around this, including having a user specify credentials as part of a flow primary inputs.
However, in a SSO environment using LDAP (AD), using the user's Username/Password to authenticate for certain operations during flows was a good feature.
We are working on an internal Portal that parses these detail before calling the OO flows using the AWESOME REST API., however, I think this should be part of the default OO webapp.
I would actually even like to access more of the "Logged In User" details.
In many cases, I want to send an E-Mail to the user kicking off the flow from Central. However, in OO 10, there is no mail attribute synchronized from LDAP.
Even just accessing the Logged-in user's DN would be ok.
Right now, OO 10 just provides the Username of the logged in user. If I want to access more information in a flow, I have to do LDAP queries.
12-13-2013 07:46 AM
The QCCR number for this issue was changed - QCCR8C21877
I wanted to make you aware of the decisions made regarding this issue:
This is the current status:
The severity of ER has been raised an opened for implementation in our next minor release. This release is scheduled to go out in the 2nd quarter of FY14.
From implementation perspective, logged-in user functionality will not be re-introduced due to security considerations (credentials are stored in OO memory). As an alternative, SSO will be used, more specifically LW-SSO.