[GH-ISSUE #32] Authentication #238

New issue

Closed

opened 2026-03-15 02:37:04 +03:00 by kerem · 2 comments

kerem commented

2026-03-15 02:37:04 +03:00

Owner

Originally created by @milankragujevic on GitHub (Apr 6, 2015).
Original GitHub issue: https://github.com/asapach/peerflix-server/issues/32

Is it planned to add some kind of authentication, so that if I use this as a seedbox or for my project (https://github.com/milankragujevic/WebMovBucket) I can have control over who's using it?

Originally created by @milankragujevic on GitHub (Apr 6, 2015). Original GitHub issue: https://github.com/asapach/peerflix-server/issues/32 Is it planned to add some kind of authentication, so that if I use this as a seedbox or for my project (https://github.com/milankragujevic/WebMovBucket) I can have control over who's using it?

kerem closed this issue

2026-03-15 02:37:09 +03:00

kerem commented

2026-03-15 02:37:15 +03:00

Author

Owner

@asapach commented on GitHub (Apr 6, 2015):

As mentioned in #18, I consider auth out of scope of this project. Today you can implement your own by placing a reverse proxy server in front of peerflix-server, e.g. nginx.

In the future I'm playing with the idea of creating an infrastructure that would allow developers to create plugins (both on the front-end and the back-end). If you have some suggestions or ideas how this should be implemented, I would appreciate for some feedback.

@asapach commented on GitHub (Apr 6, 2015): As mentioned in #18, I consider auth out of scope of this project. _Today_ you can implement your own by placing a reverse proxy server in front of peerflix-server, e.g. nginx. _In the future_ I'm playing with the idea of creating an infrastructure that would allow developers to create plugins (both on the front-end and the back-end). If you have some suggestions or ideas how this should be implemented, I would appreciate for some feedback.

kerem commented

2026-03-15 02:37:20 +03:00

Author

Owner

@milankragujevic commented on GitHub (Apr 6, 2015):

Thank you for your response. I will update my fork with a simple HTTP auth interface that can be configured from a config file, and uses a default password of admin/admin if password is not set up.

@milankragujevic commented on GitHub (Apr 6, 2015): Thank you for your response. I will update my fork with a simple HTTP auth interface that can be configured from a config file, and uses a default password of admin/admin if password is not set up.