Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

For yuuvis RAD version >= 6.12

The usage of the root user for connecting the microservices to the core-service has been replaced by a shared secret API key that is used to authenticate for the core-service internal system user that always has full rights.
Please see "How to enable system user login for microservices" for instructions on configuring the shared secret API key.

For yuuvis RAD version < 6.12

The yuuvis® RAD root user is preconfigured with every installation. The user must to exists and always has to have full rights on all object types because the yuuvis® RAD components use this user to communicate with each other. 
Thus, changing the password of this user makes changes on all yuuvis® RAD components necessary. to change the root user password, follow these steps:

  1. Got to management-studio > Organization > root-user to change the user's password.
  2. Stop all yuuvis® RAD components (services and applications).
  3. In the file <service-manager>\config\application-red.yml, change the value of the key "enaio.dms.password" to match the new password.
  4. In the file <rendition-plus>\webapps\osrenditioncache\WEB-INF\classes\config\config.properties, change the value of the key "admin.password" to match the new password.
  5. In the file <rendition-plus>\webapps\renditionplus\WEB-INF\classes\config\config.properties change, the value of the key "admin.password" to match the new password.
  6. If applicable, change the saved password in the enterprise-manager, designer, agent, and in the browser.
  7. If applicable, change the configuration of custom microservices and third-party components that access yuuvis® RAD.
  8. Restart all yuuvis® RAD components. The password has now been changed successfully.

If you or any application enters the wrong password 3 times, the user account will be permanently locked until an administrator unlocks it again. Until that time, none of the yuuvis® components can access the dms-service. This will result in failed searches or object indexing. Also, inconsistencies may emerge.

  • No labels