[FEATURE] Login authentication #57

Open
opened 2025-10-09 16:57:15 -05:00 by giteasync · 12 comments
Owner

Originally created by @olenoerby on GitHub.

What would you like to see implemented next?

I find that the service does not allow user authentication, making it annoying to not have available from a reverse proxy. Please add user authentication as a safety measure.

Originally created by @olenoerby on GitHub. ### What would you like to see implemented next? I find that the service does not allow user authentication, making it annoying to not have available from a reverse proxy. Please add user authentication as a safety measure.
giteasync added the
enhancement
planned
labels 2025-10-09 16:57:15 -05:00
Author
Owner

@olenoerby commented on GitHub:

I would suggest using basic auth configured through your reverse proxy until this actually gets implemented.

EDIT: It is possible with Cloudflare tunnels and application access policied, but yes, basic authentication would be a fine temporary solution if the user has a reverse proxy service running.

@olenoerby commented on GitHub: > I would suggest using basic auth configured through your reverse proxy until this actually gets implemented. EDIT: It is possible with Cloudflare tunnels and application access policied, but yes, basic authentication would be a fine temporary solution if the user has a reverse proxy service running.
Author
Owner

@Flaminel commented on GitHub:

I would suggest using basic auth configured through your reverse proxy until this actually gets implemented.

@Flaminel commented on GitHub: I would suggest using basic auth configured through your reverse proxy until this actually gets implemented.
Author
Owner

@olenoerby commented on GitHub:

A built in security feature will be a more secure choice for many - I am using Cloudflare tunnels through a docker environment, but not all users are this advanced.

But you are correct: Using Cloudflare Tunnels and Cloudflare Access Application policies will also do the trick.

@olenoerby commented on GitHub: A built in security feature will be a more secure choice for many - I am using Cloudflare tunnels through a docker environment, but not all users are this advanced. But you are correct: Using Cloudflare Tunnels and Cloudflare Access Application policies will also do the trick.
Author
Owner

@AlejandroAkbal commented on GitHub:

Yes, this is a must since all my arr stack is public

Besides that all other services have their own authentication

@AlejandroAkbal commented on GitHub: Yes, this is a must since all my arr stack is public Besides that all other services have their own authentication
Author
Owner

@Flaminel commented on GitHub:

If I'm not bugging you too much, why is there a need for authentication if you're already using tunnels to connect to your infrastructure? I'm guessing security is the main point of using tunnels, as opposed to opening your ports to the public.

@Flaminel commented on GitHub: If I'm not bugging you too much, why is there a need for authentication if you're already using tunnels to connect to your infrastructure? I'm guessing security is the main point of using tunnels, as opposed to opening your ports to the public.
Author
Owner

@Flaminel commented on GitHub:

Then why did you close this?

@Flaminel commented on GitHub: Then why did you close this?
Author
Owner

@olenoerby commented on GitHub:

I have started using Cloudflare tunnel and this is a working solution, but yes, having a built-in authentication frontpage would be a good addition.

@olenoerby commented on GitHub: I have started using Cloudflare tunnel and this is a working solution, but yes, having a built-in authentication frontpage would be a good addition.
Author
Owner

@Chinoman10 commented on GitHub:

Not sure which 'stack/lib' (if any) the other ARR's use, but BetterAuth provides ample options while having a stellar DX.
Ideally I'd like auth to:

  • allow bypassing auth from local requests;
  • allow disabling username+password after SSO is enabled/configured (this removes the need to setup a 'fail2ban' rule);

For now, I'm also using CF tunnels with App Access Policy.

@Chinoman10 commented on GitHub: Not sure which 'stack/lib' (if any) the other ARR's use, but **BetterAuth** provides ample options while having a stellar DX. Ideally I'd like auth to: - allow bypassing auth from local requests; - allow disabling username+password after SSO is enabled/configured (_this removes the need to setup a 'fail2ban' rule_); For now, I'm also using CF tunnels with App Access Policy.
Author
Owner

@zaphod82 commented on GitHub:

In addition, having the ability to secure the UI with a certificate would be great.

@zaphod82 commented on GitHub: In addition, having the ability to secure the UI with a certificate would be great.
Author
Owner

@olenoerby commented on GitHub:

I was not convinced you were interested in implementing the feature, but I will be looking forward to it.

@olenoerby commented on GitHub: I was not convinced you were interested in implementing the feature, but I will be looking forward to it.
Author
Owner

@Flaminel commented on GitHub:

It's marked as planned, so it will be done eventually when I get to it.

@Flaminel commented on GitHub: It's marked as planned, so it will be done eventually when I get to it.
Author
Owner

@olenoerby commented on GitHub:

I appreciate the effort, thanks mate. This is an excellent product.

@olenoerby commented on GitHub: I appreciate the effort, thanks mate. This is an excellent product.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Cleanuparr-Cleanuparr#57
No description provided.