You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m working on configuring Openfire HTTP File Upload and I’m looking for guidance on how to properly authenticate GET and PUT requests for file download and upload URLs. Specifically, I want to ensure that only authenticated users can access these URLs and perform the corresponding operations. What are the best practices or recommended approaches for implementing authentication in Openfire HTTP File Upload?
Does HTTPFileUpload provide any default configuration to provide some authentication?
Any tips or insights would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
The Openfire implementation currently does not have support for any kind of authentication. For this to be added, additional implementation needs to be realized. A primary entry point for this would be around the SlotProvider API.
I’m working on configuring Openfire HTTP File Upload and I’m looking for guidance on how to properly authenticate GET and PUT requests for file download and upload URLs. Specifically, I want to ensure that only authenticated users can access these URLs and perform the corresponding operations. What are the best practices or recommended approaches for implementing authentication in Openfire HTTP File Upload?
Does HTTPFileUpload provide any default configuration to provide some authentication?
Any tips or insights would be greatly appreciated.
The text was updated successfully, but these errors were encountered: