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

The Firefly III Data Importer does not require any authentication to use. This means anyone with the URL can start importing CSV files.

I run the fireflyiii/data-importer container on a separate server with Traefik as the reverse proxy and Authelia (for ForwardAuth) to force logging in. This is probably overkill for a single user and why I recommend just running this from your workstation. Docker and docker-compose need to be installed.

Copy the docker-compose yaml below and enter your environment variables. Save it in a folder on your workstation.

docker-compose.yml:

version: '3' services: app: image: fireflyiii/data-importer:latest container_name: firefly-iii-data-importer restart: unless-stopped environment: # See https://docs.firefly-iii.org/data-importer/install/configure/ - FIREFLY_III_URL=https://sub.domain.tld - VANITY_URL=https://sub.domain.tld - FIREFLY_III_ACCESS_TOKEN=ey........... #- FIREFLY_III_CLIENT_ID= #- NORDIGEN_ID= #- NORDIGEN_KEY= #- SPECTRE_APP_ID= #- SPECTRE_SECRET= ports: - 8081:8080

Once you've modified the file with all of your environment variables you just need to navigate to the folder containing the docker-compose file in a terminal and run docker-compose up -d. This will start the container in detached mode. Once it is up and running you can access the data-importer at http://localhost:8081/

When you're done importing you can go back to the directory with the docker-compose file and run docker-compose down to stop the container.

I can share my Traefik labels for anyone interested in setting up Forward Auth through Authelia.

Hope this helps!

The main reason is that their rewrite of the LDAP connector does not work anymore and is pending fixes. I had some attempts to contribute a fix, but I so far lack the in-depth knowledge of the PHP frameworks used. It is still on my list to hopefully be able to contribute a fix. You can track the upstream issue at https://github.com/firefly-iii/firefly-iii/issues/5133

I have added a note in the docs and in the UI as well.

Oh looks like you reported it already at https://github.com/firefly-iii/firefly-iii/issues/4960 . But it seems you are not running Cloudron at all. This is a forum for apps installed using Cloudron and not a general app support forum for Firefly III. The github issue tracker is the correct place.

@hillside502 done!

This is issue is now fixed ! thanks a lot !!! 🙂

Screenshot.png

Right now with cloudron, some apps supports LDAP, some don't.

If I need to do a cloudron setup comprising apps that are all LDAP, I of course use LDAP in order to get one login to rule them all.

But if I do a cloudron setup where an app is not LDAP, I prefer to have all app not using LDAP.
It's confusing to have to explain to people that for those X apps, you need to use the same login, but for those X apps, it's separate logins, even though it's all based on the same main domain.

That's why I prefer to have both LDAP and non LDAP version of an app available.

In the case of Firefly, I think LDAP is even less useful, because it's personal finance and probably less useful in an organization context. For example, if I want to give a Firefly instance for a friend, I don't need to have an additional LDAP user. I'd prefer to have the friend has its own login with the app.