Solved Unable to login after upgrade to Firefly III 5.6.10

[colonelpanic]

Hello,

I am no longer able to log in to Firefly III after upgrading to 5.6.10. I get a warning at the login screen that says, "Please upgrade LDAP configuration"

Should I go ahead and follow the instructions in the Firefly III documentation? My original username/password does not work, nor does my Cloudron username/password (LDAP). Please advise.

Thanks in advance.

[colonelpanic]

Just to clarify. It was upgraded from 2.2.9 to 2.3.0 according to the Backups section of the Firefly III app. See screenshot below:

[girish]

@colonelpanic The LDAP authentication changed drastically in Firefly 5.6. I tried to put in auto-update code to migrate from old LDAP to new LDAP. Maybe I made some mistake in the migration, let me check again.

[girish]

https://github.com/firefly-iii/firefly-iii/issues/5133 is the upstream issue in case you wonder what changed.

[colonelpanic]

@girish, thanks for looking into this. I attempted to follow the thread before making this post. I found it in the package updates thread. However, I was able to follow along until this reply.

Please let me know if there is anything I can provide to assist with the troubleshooting.

Thanks again.

[joni-menahem]

@colonelpanic said in Unable to login after upgrade to Firefly III 5.6.10:

oking into this. I attempted to follow the thread before making this post. I found it in the package updates thread. However, I was able to follow along until this reply.

did you manage to solve it ? I'm having the exact same problem..

[colonelpanic]

@joni-menahem, I did not. I restored a backup for the time being and I will try to dig into it some more this weekend.

[girish]

@colonelpanic @joni-menahem for the moment, please roll back and disable automatic updates, I am looking into this now.

[girish]

OK, so picking some old release and updating all the way, I see:

Strange, why the tests work because we test exactly this in the tests... but manually it does fail.

[girish]

I have revoked this latest package, the whole block of env variables has changed. I think I made some mistake when running the tests. Fixing up now.

[girish]

@colonelpanic @joni-menahem I have pushed a new package 2.3.0-1 , can you please check?

[colonelpanic]

@girish - that did the trick. I upgraded to 2.3.0-1 and I can log in as before.