Issues

 
1 of 1

regression: when migrating from 5 to 6, a datasource with an empty password throws an admin error

Fixed

Description

using a mysql 8.0.33 datasource in admin

  1. open the datasource, save it, shows ups as ok

  2. select the datasource and verify it, shows error

  3. or access the database, an error relating to password is shown

  4. open the datasource and save it again,, it says ok

  5. repeat 2 or 3, same error

lucee is running in multi context mode

this is using preside (which hides datasource errors OOTB )

Environment

None

Attachments

3

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Created 29 May 2023 at 13:55
Updated 9 June 2023 at 15:32
Resolved 9 June 2023 at 15:32

Activity

Zac Spitzer2 June 2023 at 14:18


(to test simply delete the password key from a datasource in cfconfig.json

Zac Spitzer2 June 2023 at 07:12

added a null check, also I improved the verify to show the error inline, rather than only as a tooltip

Zac Spitzer30 May 2023 at 16:13
Edited

ok problem is with an upgrade from 5 to 6, a migrated datasource without a password causes the above error

Zac Spitzer30 May 2023 at 13:55
Edited

in the datasource definition in CFconfig.json, the password key was missing completely, hence the null?

can’t repo via the admin UI, need to investigate how to repo. deleting the password from the datasource definition manually repros

Michael Offner30 May 2023 at 13:54

the issue only happens when you have a datasource with the same name in the Lucee Server and web context with different passwords?

I was no able to reproduce the issue, based on the information in the description. i was following the instruction 1 to 1, but was not able to reproduce the issue.