Legacy Knowledge Base
Published Sep. 10, 2025

Should OSGi config files and the values in the System Settings application always be in sync?

Written By

Tímea Bihari

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

  • I have a module where I do not want to store sensitive data (eg. password) in the config file
  • I would like to provide this value over the UI in System Settings
  • Is it possible to use a "mixed" approach?

Environment

  • Liferay DXP 7.0+

Resolution

  • It should not be possible to use the mixed approach (when you provide some configuration values in the config files, while others are provided in System Settings).

  • Liferay will keep the OSGi config file and the values on the UI in sync. When the configuration is modified on the UI, the config file is updated with the new value. If the config file is modified, then the values on the UI are updated.

  • We advise to use the single source approach: either update the configuration on the UI or use the config files.

  • "Mixed" configuration should not be used. Due to unforeseen issues, it might happen that the settings come out of sync. In such cases, you can easily lose previous settings.

Additional Information

 

Did this article resolve your issue ?

Legacy Knowledge Base