Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-3187

deactivation throws error and seems like bug in the workflow module

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Outdated
    • Icon: Major Major
    • None
    • 4.3.1
    • activation, workflow
    • test local instance on windows xp workstation running tomcat 5.5.27

      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.

        Acceptance criteria

              Unassigned Unassigned
              venkimcg Venki Ramaratnam
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD