Add authentication capabilities to NIPM feeds

[Nicolas_Bats]

It could be usefull to have authentication capabilities in NIPM in order to create private feeds. Feeds stored on Microsoft Windows folder / shared folders can use Windows authentication but there is nothing available for feeds accessed with HTTP requests.

Something like username/password or API Key in HTTP headers, if possible a mechanism to be compatible with all storage plateforms (AWS, Artifactory...).

[andre.buurman@carya]

The product won't be mature without it. E.g. when I'm going to use Systemlink with the org model it allows me to guard of access to a repo, but only internally. Server to clients. Once the url is deployed to targets anyone can access it via package manager,  not a nice thought. Add security capabilities in the light of systemlink use cases for securing and separating access to hosted resources.

[felipefoz]

Do we have any progress on that? Or is still in consideration?

[JoGra]

Hi, 

I would also like to ask for an update on this feature. 

We deploy apps through the very convinient no package manager, but the missing  authentication means that no secure feed can be used to distribute updates.

Simple API key compatible with s3 would be ideal.

Thank you! 

[Scott_Richardson]

Hi @JoGra and felipefoz, who more recently added comments with interest in this capability. We have not been able to prioritize this yet, but it is something that we are interested in supporting. I cannot give any more specifics at this time. Note that a predecessor requirement to supporting authenticated feeds will be to prevent NIPM from blocking any redirected URLs used when downloading package files from these types of hosting services. 

[JoGra]

Hi Scott,

Thanks for the feedback.
I understand that more work might be necessary, as originally the NIPM was intended to distribute the NI packages. 
Maybe some of the work how systemlink server acess an S3 bucket could be utelized?

Best regards,

Jonathan

[Bas.v.E]

I was wondering if there is any news about this feature as the development has been started in 2020 already

[CyGa]

+1