PublishTransaction event does not publish the component with user id instead it is publishing with system user account

Question

When a component is published successfully, we want a related component to be auto published (am not going into the details of why we need this). We are trying to implement this through event system.

this.EventSystem.SubscribeAsync<Component, SetPublishStateEventArgs>(this.OnComponentSetPublishState, EventPhases.Initiated);

Though the related component is added to the queue, it is added to the queue by system user ""Tridion Content Manager System NT Authority User", not by the user who actually published the first component. Is there a way by which we can have the related component added to the publishing queue by the actual user? Version: SDL WEB 8.5

Answer 1

Publish transaction gets created by the user, but the actual publishing happens in the Publisher service under the system account (the one that runs the Windows service). That account is used (among other tasks) to set publish states on published items. In order to send another item to publish on behalf of the original user, you need to create a new Session using the username of the original user and create new PublishTransaction using the new session.

Make sure the System NT Authority User is configured to be impersonation user.

Answer 2

In order to use Impersonation, I guess you would need to add all the users that may publish this content type as an impersonation user in Tridion Impersonation Users.

IIRC you also have to allow a change to the Local Security Policy to bypass traverse checking.

I would suggest one of two other options

1. You could elevate the user during the event and publish the target Component
2. You could keep a field (and therefore easily seen in component history) by updating the target component and then publishing it {of course - it's not clear if you've a 1:1 relationship of *:1 with the target Component being published many times}

The reason I add 2 is that I saw a similar requirement some time ago and we had to take account of the fact that:

• the publish queue is trimmed and republishing that component to the same target will overwrite the previous instance {i.e. you only know who published it last}
• there was no scope to write a fancy publish tracking system
• the audit team had access to content but didn't have/want access to publishing data directly anyway {the published by/on was field that lived with the historical versions of that Component and was easy to see was version of content was published by whom at a specific point in time}

Answer 3

this.EventSystem.Subscribe<Component, SetPublishStateEventArgs>(this.OnComponentSetPublishState, EventPhases.Initiated);
    private void OnComponentSetPublishState(Component subject, SetPublishStateEventArgs e, EventPhases phase)
    {
        var publishInstruction = new PublishInstruction(subject.Session);
        var targetTypes = e.Target.TargetTypes;
        PublishEngine.Publish(new[] { subject.Session.GetObject("tcm:882-1053226") as Component }, publishInstruction,
            targetTypes);
    }