Passing variables to a POST request from an outside controller

Since you guys have been very helpful in my early steps into the Play Framework (thanks for that), here it goes again:

We have a working registration controller, that POSTS all credentials to the database.

But then, we want to make it possible to be immeadiately logged in afterwards. Below is the code that makes this work:

    public static void doRegistration(@Valid User user) {

//registering the user

    try{
        SecureCont开发者_Python百科roller.authenticate(user.username, user.password, false, "MainController.index");
    }catch(Throwable ex){
        MainController.index();
    }

This works fine, but it is not very safe because it GETs all the credentials to the server. I know I have to edit my routes file somehow, but I can't see how.

The routes file:

*       /account                                SecureController.login
POST    /account/register                       RegistrationController.doRegistration
GET     /account/register                       SecureController.login

Somewhere should be the action SecureController.authenticate, but what do I have to put in the column after the POST... It can't be /account/register, because that fails...

Thank you beforehand!

I am not sure I understand your issue. The routes file is just a way to configure your URLs to be pretty URLs. If you don't specify them, then it falls back on default {controller}/{method} syntax.

The issue you are having, is that when you call another controller Play performs a redirect to that controller's method, which involves sending a request back to your browser telling it to redirect (this ensures that the state of the application is reflected in the URL within the browser). A redirect needs therefore to send a GET request, and included in the GET request will be your parameters.

what you are trying to do, as you said, is not safe. What you should do (not the only option, only one possibility) is:

• Maintain your current doRegistration action for the user
• Create a service class (that does not inherit Controller). It can be static or require instantiation (with static methods should be enough though).
• Add a @Before method to a common controller that will be executed always. One way is to create a controller with a @Before method and add this controller to all other controllers via the @With annotation, so that @Before will be executed always for all controllers. It requires you to add a @With to each new controller, but I believe it keeps the code quite clean.

The idea would be that the controller calls the authenticate method from the service class. It's a simple static This method checks the user (if it's enabled, has proper license, whatever) and sets some parameters in the session (via Session object).

To help with this you may want to create another authenticate method in the user that returns the attributes to set (for example in a Map, if it contains an "error" key the user can't be authenticated for some reason). How to do this step can change according to your requirements.

Once the Session has been set, you redirect to the page of your election (main, profile, etc). As you have the common @Before method, this will be executed. This method should verify the credentials in the session (user authenticated, license type, etc) and act accordingly. You have an example in the Secure controller of Play, but you could create your own.

With this, you could user the authenticate method of the service from any controller, allowing authentication via multiple methods, and using a common point to verify the session.