[BUILD-703] Database password encoding issue at install time Created: 01/Mar/22  Updated: 21/Jun/22  Resolved: 20/Jun/22

Status: Closed
Project: Build
Component/s: None
Affects Version/s: BOM 5.7.19, BOM 6.2.20
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Carlos Cantalapiedra Assignee: Federico Grilli
Resolution: Workaround exists Votes: 0
Labels: foundation_team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
relation
Template:
Acceptance criteria:
Empty
Date of First Response:
Team: Foundation

 Description   

Steps to reproduce

  1. On a Magnolia 5.7.15 instance setup mysql configuration
  2. At jackrabbit-bundle-mysql-search.xml file, set the password Base64 encoded as explained here
  3. Start magnolia and check that the following error is thrown:

    Caused by: java.sql.SQLException: Access denied for user 'root'@'localhost' (using password: YES)

Expected results

The Magnolia instance starts normally

Actual results

Exception is thrown

Workaround

  • Install Magnolia with a PersistenceManager setup not requiring a password
  • Once deployment is complete, switch to mysql with encoded password

Development notes

  • Debugging shows that things actually blow at org.apache.jackrabbit.core.util.db.ConnectionHelper.getExtraNameCharacters(ConnectionHelper.java:185) since at that stage the password hasn’t been decoded yet
  • Looks like a JackRabbit issue, not Magnolia's.


Slack https://magnolia-cms.slack.com/archives/CDF2T239Q/p1646124892266279



 Comments   
Comment by Federico Grilli [ 20/Jun/22 ]

Updated description with workaround/debugging info and closing for now. It looks like we can't do much on Magnolia's side, if not patching JR.

Feel free to reopen anytime, of course.

Generated at Sun Feb 11 23:44:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.