Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Unable to configure instances using portal-{WebID}.properties

Written By

Ankit Gupta

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.

Issue

  • Steps to Reproduce

    1. Add -Dcompany-id-properties=true to the JAVA_OPTS on $LIFERAY_HOME/tomcat/x.y.z-bin/setenv.sh;
    2. Add a file $LIFERAY_HOME/portal-test1.properties with the content company.security.auth.type=screenName;
    3. Go to Configuration > Virtual Instances;
    4. Create a new virtual instance with the Web ID "test1";
    5. Access the virtual instance by its virtual host (may require fiddling with /etc/hosts);
    6. Login on the instance;

    Expected Results

    The login screen asks for the user's screenname, because of the property company.security.auth.type=screenName added to portal-{web-id}.properties.

    Actual Results

    The login screen asks for the user's email, showing that the property from portal-{web-id}.properties was not loaded.

Environment

  • Liferay environment details, as well as third party and/or recent changes to environment that are relevant

Resolution

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?