LDAP Authentication appears to not function after a node restore.
book
Article ID: 100032968
calendar_today
Updated On:
Cause
LDAP authentication requires additional initialization time after a node restore.
Resolution
How to determine when a node restore is complete:
1. Perform node restore: do not exit.
Note: After the node restores completely, restart services
2. Monitor the .txt file that is generated for completion of the upgrade task. The file is named
esadb_
.txt, where is an automatically generated file number. It is located under
/upgrade/reports/evidence_repo_.
3. Locate PropertyUpgradeTask. Once the report displays " Upgrades Successful!", users will be able to login
via the LDAP credentials.
Example:
# 2016-07-31 16:15:22,973 Executing com.teneo.esa.common.util.PropertyUpgradeTask
.
.
# 2016-07-31 16:15:23,660 Upgrading: default.properties
# 2016-07-31 16:15:23,661 Applying script: Properties Upgrade.esa.ldap.connectionPassword to file:
D:\CW\V82\config\configs\default.properties
# 2016-07-31 16:15:23,664 Applying script: Properties Upgrade.esa.system.support.privilegedPassword to
file: D:\CW\V82\config\configs\default.properties
# 2016-07-31 16:15:23,760 Finished applying script: Properties Upgrade.esa.ldap.connectionPassword to
file: D:\CW\V82\config\configs\default.properties
# 2016-07-31 16:15:23,761 Finished applying script: Properties
Upgrade.esa.system.support.privilegedPassword to file: D:\CW\V82\config\configs\default.properties
# 2016-07-31 16:15:23,763 No changes in D:\CW\V82\config\configs\default.properties
# 2016-07-31 16:15:23,765 Upgrades successful!
Issue/Introduction
A node backup taken from a previous version will restore completely. The LDAP authentication is not available immediately after the restore because additional time is required to fully initialize.
Additional Information
JIRA: ESA-44773
JIRA: ESA-45036
Was this article helpful?
thumb_up
Yes
thumb_down
No