[MAGNOLIA-3187] deactivation throws error and seems like bug in the workflow module Created: 23/Apr/10  Updated: 04/Dec/13  Resolved: 04/Dec/13

Status: Closed
Project: Magnolia
Component/s: activation, workflow
Affects Version/s: 4.3.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Venki Ramaratnam Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: /activation, workflow
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

test local instance on windows xp workstation running tomcat 5.5.27


Attachments: Text File activation-bugsend apr-23-2010.txt    
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Hi
We are using domino LDAP to authenticate ! I am testing the workflow so that I can device workflow for my organization.
When a user initiates the activation -> goes to the publisher group -> publishers activates . This works. The problem here is at the time of activation internally it uses the superuser account as a proxy and activates the node /page and working fine.
The issue becomes ugly because of the proxy when deactivating ! The deactivating doesn't seems to use the proxy mechanism and hence throws the error and can be deactivated by the super user.
Also if super user accounts have different password on both the author instance / public instance both activation /deactivation do not work .
Is there a way not to use superuser account at all for activation /deactivation process .
Please see error log attached.


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