[MAGNOLIA-1644] Support activation in SSO environment Created: 27/Jul/07  Updated: 13/Mar/12  Resolved: 13/Mar/12

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 3.1 M1
Fix Version/s: 4.5

Type: Improvement Priority: Major
Reporter: Sameer Charles Assignee: Jan Haderka
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

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


 Comments   
Comment by Magnolia International [ 06/Nov/07 ]

status ?

Comment by Magnolia International [ 22/Nov/07 ]

Sameer, please provide status and edit fix version appropriately.

Comment by Magnolia International [ 26/Nov/07 ]

ok - nothing has been concretely done, but needs review with regards to latest context changes.

Comment by Jan Haderka [ 13/Mar/12 ]

Fixed by MAGNOLIA-3904

Generated at Mon Feb 12 03:28:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.