[ http://jira.magnolia.info/browse/MAGNOLIA-1644?page=comments#action_15190 ] Grégory Joseph commented on MAGNOLIA-1644: ------------------------------------------
ok - nothing has been concretely done, but needs review with regards to latest context changes. > Support activation in SSO environment > ------------------------------------- > > Key: MAGNOLIA-1644 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1644 > Project: Magnolia > Issue Type: Improvement > Components: activation > Affects Versions: 3.1 M1 > Reporter: Sameer Charles > Assigned To: Sameer Charles > Fix For: 3.5 RC2 > > > Activation command uses current logged in user or the system user in case of > workflow to authenticate against > the subscriber. this works in standalone systems where magnolia is a master > application and you have logged in to it, problem arrises > once you move to SSO environment where magnolia may or may not be the master > and do not have access to the user credentials. > IMO: > - if workflow is active, we should use the credentials of the user who is > proceeding the workitem (participant), or the defined user in > workflow definition > - In case of direct activation, use system user and impersonate as the logged > in user -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
