Remote publishing only checks the first Liferay instance for user permissions

• Type: Bug
• Status: Closed
• Resolution: Duplicate
• Affects Version/s: 6.1.20 EE GA2, 6.1.X EE
• Fix Version/s: 6.2.0 CE GA1, 6.2.10 EE GA1
• Component/s: Staging
• Labels:
  • ee-ts
• Environment: LIFERAY VERSION: 6.1 GA2 ; OPERATING SYSTEM: Windows Server 2008 ; APPLICATION SERVER: Tomcat 7.0 ; JAVA VIRTUAL MACHINE: Java 6 ; DATABASE: SQL Server 2008 R2

1. Setup two Liferay nodes, 1 staging and 1 remote live
2. Edit your hosts file to point 127.0.0.1 to me.com
3. Start the remote live instance and login
4. Create a new Liferay instance on the remote live instance: me.com
5. Go to me.com:8080 and login
6. Go to Control Panel > Site Settings and note the site ID.
7. Start the staging site and login
8. Add pages and content as desired
9. Change your admin user to have the same exact Screen Name, Email Address, Password, and, First and Last name as the user in the remote live (me.com) instance
10. Go to Control Panel > Site Settings > Staging
11. Enable Remote Live staging pointing to your remote live (me.com) instance using the IP Address (in this case 127.0.0.1)
12. Notice how Remote Live staging cannot be enabled
13. Enable Remote Live staging just like step 11, but use the domain instead of the IP address (in this case me.com).
14. Notice that Remote Live staging is enabled
15. Now, go to the first instance of Liferay on the Remove Live instance and modify the admin user to match the publishing user on the Staging node
16. Attempt to alter the staging setup on the staging node and use the IP address
17. Notice that it now enables with the IP address