Working with Login Routes

The login module lives at the URL login/login by default. While this works fine, you may prefer a shorter or more branded path for your users — /admin, /sign-in, or anything else that suits your application.

This page covers how to configure custom routes for the login module and how to handle unauthenticated access to protected pages.

The Default Login URL

Out of the box, the login module is accessible at:

All login-related functionality sits under this module:

Setting a Custom Login URL

Open config/custom_routing.php and add a route that maps your preferred URL to the login module:

Now, visiting /admin displays the login form, and the form submission is handled correctly through the custom route.

Including All Login Actions

If you want to route all login module actions under your custom path, add entries for each action:

With these routes in place, your users see clean URLs like /admin and /admin/logout while the login module handles all the authentication logic behind the scenes.

Redirecting Unauthenticated Users to Login

When an unauthenticated user tries to access a protected page, the system needs to know where to send them. The login module handles this through the redirect_on_success and login-check methods, but you can also use Trongate's built-in redirect() helper:

Alternatively, use the security module to let it handle redirection:

The Security Module and Custom Routes

The trongate_security module's default scenario checks for a valid token and redirects to login/login if none is found. If you have set a custom route for login, the security module will still redirect correctly because the login module is doing the actual work.

For scenarios where you need a different redirect behaviour, you can override the default scenario in your Trongate_security.php controller:

Configuration Options

The login module's behaviour is configured in config/login.php. The most relevant settings for routing are:

Practical Example: Admin Panel

A common setup is to use a custom route for the admin login and a separate route for the members area:

With this configuration:

• Administrators visit /portal to log in
• They are redirected to trongate_administrators/manage after successful login (as configured in config/login.php)
• The logout link becomes /portal/logout
• The forgot-password flow runs through /portal/forgot_password

This gives your application a clean, branded authentication experience without exposing the underlying module structure.