# Login Engine

**URL:** <https://www.ruby-forum.com/t/login-engine/102388>\
**Category:** Engines\
**Created:** [February 8, 2006, 2:27pm UTC](https://www.ruby-forum.com/t/login-engine/102388 "2006-02-08T14:27:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vegard](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/6f9a4e/32.png) [@Vegard](https://www.ruby-forum.com/u/Vegard)\
**Post date:** [February 8, 2006, 2:27pm UTC](https://www.ruby-forum.com/t/login-engine/102388/1 "2006-02-08T14:27:39Z")

</div>

Hi, I’ve been using the login engine for a web application I’ve  
developed, but I’ve run into a small problem.

Using before\_filter on other controllers works just fine, but I also  
want methods in the UserController that is included in the Login Engine  
to be protected in some cases. For instance, I’d like the signup action  
to be unavailable unless a user is logged in (only valid users can add  
new accounts). I’ve added the normal before\_filter to the  
UserController, but this is obviously not the correct way of doing  
this.

So in short: how can I secure all actions except login in  
UserController?

My thanks in advance for any help you can give

Regards,  
Vegard