How to integrate client authentication to usenet?

[sarausenet]

Hello everyone ,
if you please , I want to ask about how to authenticate the client that uses usenet to download a file of type nzb from my web site .the case is as follows:
the client should enter a user and password , if this user is registered to my web site , he could download the file through usenet
I want to ask also if it is possible to create the authentication part by c# as an api , and then drag it to usenet or not ? and if it is possible ,how to drag the library to usenet .
if you please any help would fit from you
Thank you very much

[exussum]

keep sab accessible from inside the network only (or even local). then use the sab api to add nzbs to it. The checks can be done using mysql and php. You can keep a log of nzb files added this way too

[inpheaux]

if this user is registered to my web site , he could download the file through usenet

This is nowhere near as easy as you think it is, and SABnzbd is probably not the right tool for the job. Technically you could rig it up such that through your website users could blindly queue up NZBs in some centralized SABnzbd installation, and use specific post-processing scripts as a callback method to your application to handle moving files and letting users know that their stuff is done, but SABnzbd doesn't do any kind of multithreading, so how would you handle queue management?

Giving each user their own SABnzbd installation on your back-end wouldn't be feasible, since each one would slow down everyone else's speeds. But leaving it all in one queue would mean the workflow would be:

1) User comes to your site, queues up one or more nzbs
2) These nzbs are queued in your centralized SABnzbd installation
3) User has to wait an indeterminate length of time -- possibly FOREVER if the download fails -- for their file to be ready to download
4) User gets pissed off and leaves

I understand that you're trying to find a way to sell sabnzbd-as-a-service, but I seriously doubt you're going to be able to really be any easier or faster than a user just running SABnzbd themselves.

[exussum]

inpheaux - though the front end you could either use the API to get a estimated download time or You could use the Post process script or even connect to the sqlite database directly. Assuming the sab box is on a differnt server so sab wont slow down http processes etc it should be workable

[inpheaux]

inpheaux - though the front end you could either use the API to get a estimated download time or You could use the Post process script or even connect to the sqlite database directly. Assuming the sab box is on a differnt server so sab wont slow down http processes etc it should be workable

It still won't scale and won't produce anything remotely enjoyable for an end-user. The OP sounds like a guy who came by #sabnzbd a few weeks back, who wanted to find a way to sell sabnzbd-as-a-service, and couldn't seem to wrap his head around the fact that it is a terrible terrible idea that gets worse with every user you add, and furthermore couldn't wrap his head around the fact that it wouldn't be a super friendly process to implement. He seemed to think you'd just implement third party auth and them boom all of a sudden people could come in to his site and magically PRESS BUTTON FOR USENETS.