Easy installer feature request: Support HTTP Basic access authentication

As we have multiple projects which are not all public but we want to make them accessible in a comfortable way for specific users through Toradex Easy Installer, we want to set a feature request for Toradex Easy Installer to support at least HTTP Basic access authentication to access image source files.

Thank you in advance!

Hi @ost

Welcome to the Toradex Community!

As described on our developer website about Toradex Easy Installer, this tool should be used in a safe requirement.

May I know what is your application?

Best regards,
Jaski

@jaski.tx

Hi Jaski and thank you for getting back to us.
Maybe I was not clear enough, apologies.
We are not using Toradex Easy Installer in an unsafe environment, it’s only used inside our internal LAN.
But as we are a big company with many projects and different independent departements it would be very useful to have at least a simple basic HTTP authentication implemented into Toradex Easy Installer so that installing images (such as Yocto based images in our case) could be webserver-user dependent.

To be more clear:
Currently it is only possible to add HTTP sources without user authentication to the Toradex Easy Installer. This means all source image files must be stored at least on a web server with public access (where “public” means accessible for all our internal users in our case).
That said, when using Toradex Easy Installer, our goal would be to have the possibility to add HTTP sources with a simple HTTP user authentication.

Best regards.

Hi @ost

Thanks for the information.

But as we are a big company with many projects and different independent departements it would be very useful to have at least a simple basic HTTP authentication implemented into Toradex Easy Installer so that installing images (such as Yocto based images in our case) could be webserver-user dependent.

Does this mean that specific images should be available depending on a specific user?

This means all source image files must be stored at least on a web server with public access (where “public” means accessible for all our internal users in our case).

Why this solution is not acceptable?

Best regards,
Jaski

Does this mean that specific images should be available depending on a specific user?

Exactly!

Why this solution is not acceptable?

Because of projects which are bound on privacy policies. A simple basic HTTP authentication implemented into Toradex Easy Installer would solve the issue of havin this problem.

Hi

Thanks for your answer. I opened a Ticket internally and I will come back to you once I have more Information.

Best regards,
Jaski

Hi @ost

So I checked with the R&D Team and we are not planning to implement this feature in near future. I am sorry that I cannot provide you a better answer for the moment.

Best regards,
Jaski