-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sap_swpm: hdbuserstore default entry changed incorrectly in the post installation steps #747
Comments
Pull request #748 |
@rob0d Original code is from PR #446 describing If everything is taken care of, please close this GH Issue |
@sean-freeman I think we need the code (or similar) you pasted in PR #802 for this to be closed and correct. As this PR on it's own introduces a problem when |
@rob0d Let's consolidate the discussion in one place and close this GH Issue? |
Hi guys, over the past few weeks I was trying to do installs in a more secure way with different passwords for different users (rather than the same for everything) and I've found a few problems :). Some may be bugs in swpm and I am still investigating that. Presumably it will be best to create separate issues and pull requests for each? So this is the first one.
SAP SWPM Post Install - Enforce Connection Info in SAP HANA Client hdbuserstore is inserting incorrect password for the SAPHANADB user. This completely kills the system as the hdbuserstore is changed after SAP started (so it's not obvious), but when it's restarted or new connections are made the SAPHANADB user gets locked and the ABAP instances obviously die/hang.
I don't understand why is this step required? hdbuserstore is correctly populated by SWPM and everything works. How does it relate to host agent?
Anyway,
sap_swpm_db_schema_abap_password
(SAPHANADB schema password) should be used instead ofsap_swpm_db_system_password
(user SYSTEM password).The text was updated successfully, but these errors were encountered: