Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

WeDeploy Auth Admin Portlet in Liferay DXP 7.0 Fix Packs

Written By

Nicole Mak

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

When deploying Liferay DXP 7.0 Fix Pack 24, 25, 26 or 27, the WeDeploy Auth Admin portlet will appear in the Control Panel. WeDeploy is currently a beta product. The addition of this portlet will have no impact or security risk. 

Installing an affected fix pack will result in the following unintended changes: 

  • The WeDeployAuth_WeDeployAuthApp and WeDeployAuth_WeDeployAuthToken tables are created
  • ResourceAction and ResourcePermission entries for the WeDeploy Auth Admin portlet are added

Resolution

WeDeploy Auth Admin portlet has been removed from DXP 7.0 Fix Pack 28. Customers who have not applied Fix Pack 24, 25, 26 or 27, and skip to applying Fix Pack 28+ will not be affected by this issue.

Customers who have applied Fix Pack 24, 25, 26 or 27, and wish to remove the WeDeploy Auth Admin portlet can follow these steps:

  1. Download the drop_wedeploy_tables_and_data.sql file
  2. Verify that the tables from the SQL file have appeared in the database
  3. Backup the system database
  4. Run the SQL file
  5. Verify that the database tables have been deleted
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?