Data Importer Tool

[girish]

@JLX89 said in Data Importer Tool:

There doesn't seem to be an authentication gateway to prevent "public" access and your Personal Access Token is embedded in the .env file.

How is this usually done upstream? Note that you have access to the htaccess file, so you can put an basic auth guard in place.

[JLX89]

@girish I didn't actually see much mentioned about how it's completed upstream. There is a public instance setup run by Firefly. I ended up going the .htaccess route and need to finish a few other configuration items to ensure the .htaccess hasn't interfered with anything.

[robi]

@JLX89 NIce, when you're done, please post the contents of the .htaccess config for future readers.

[JLX89]

@robi Sorry for the delay on this! I ended up going the .htaccess / .htpassd route to secure it for the time being.

It would be great if we could use the proxyAuth option and use that as a "drop in" for a LAMP stack.

[robi]

@JLX89 and the contents of .htaccess?

[JLX89]

I'm using pretty much the standard, the default .htaccess that comes with the data-importer tool, and the generated .htpasswd file I created. I've just added the below. Just update the # Whitelist API Requests line with API requests from the services you're using with the data-import tool.

# Password Protect Entire Directory
AuthName "Restricted Access" 
AuthType Basic 
AuthUserFile /path/to/.htpasswd 
require valid-user
# Whitelist API Requests
Allow from api.domain.com

[cylon]

@JLX89 said in Data Importer Tool:

9. Restart the LAMP App and you can access the interface at: https://firefly-importer.domain.tld

Many thanks for this, very helpful !
However after doing all this configuration, I cannot access to the data-importer at https://firefly-importer.{my-domain.tld} I have a DNS error.

I don't see in the .env where the URL is set ? Also, I guess I need to create manually add an entry to my DNS record for the firefly-importer sub domain ?

[JLX89]

@cylon Did you update the app "public route" in your Apache configuration from /app/data/public to /app/data/data-importer/public and restart the app? You'll also want to double check the permissions:

sudo chown -R www-data:www-data /app/data/data-importer
sudo chmod -R 775 /app/data/data-importer/storage

The DNS is handled by the LAMP app from the settings you chose when you deployed the app.

[cylon]

oh ok I thought I had to use https://firefly-importer.{my-domain.tld} but it actually is https://{my-lamp-subdomain}.{my-domain.tld} my bad

so it's actually working just fine thx

[JLX89]

@cylon Great to hear!

[dadams-AU]

hey - i tried to build this a couple of times. i keep getting a 403 apache error. any thoughts?

[robi]

@dadams-AU fix your apache config?

[JLX89]

@dadams-AU More than likely along the lines of what @robi said.

You'll need to retrace your steps and ensure you completed the configuration change in the public routes in /app/data/apache/app.conf and ensure that you set the permissions correctly using:

sudo chown -R www-data:www-data /app/data/data-importer
sudo chmod -R 775 /app/data/data-importer/storage

If you haven't restarted the LAMP app, you'll need to do that before all of the previous settings work correctly.

[jadsmrizk]

Hello all!
I am following this tutorial but apparently, recent versions of the data importer tool require PHP 8.3 which isn't supported by the LAMP app. Any workarounds?

Thank you

[girish]

@jadsmrizk The latest lamp app has 8.3 now

[jadsmrizk]

@girish thank you. Will give it a try