Cause

or the password entered in replication agent transport configuration doesn't match the user's password on the publish instance

On Reverse Replication, this would be caused by the same issue for the "Agent User Id" on the reverse replication user agent.

Resolution

To fix this issue:

For forward replication:

Make sure the user configured in the replication agent Transport tab on the author instance exists on the publish instance. If the user doesn't exist, then log in to the publish instance and create the user.

Validate that the password entered for the user correctly matches what is configured on the publish instance.

Check the permissions of the user on the publish instance and make sure that the user has write permission for the paths that are being replicated. Use http://host:port/useradmin UI to add necessary permissions.

For reverse replication:

Ensure the Agent User Id is set and not left blank on the Reverse Replication Agent settings.

The Agent User Id chosen needs to have the correct ACLs to have write access on the Author instance when pulling data from the Publish instance.