How to redirect after a login success or fails in loopback

[Mrinal Purohit]

I have created a loopback and successfully able to connect to mongo as a datasource.

I created a user and then tried to login. It worked perfectly. As soon as I login from my login screen, I get this:

{

• id: "gxLjLWWozMCk8HLuOuGrhSCqIkIUzAbruwkHAwKaB8TlOIA565tyUnuwlh99kHTF",
• ttl: 1209600,
• created: "2014-12-07T04:46:33.900Z",
• userId: "5483c9d6e97d2c6b04ae8798"

}

This means that I was able to login properly. I am using standard route api/Users/login

I don't want this screen to show up. I need to redirect the user to some dashboard. In case it fails, it should redirect it back to the login screen.

[Brian Bagdasarian]

Add a hook for the redirect that fires after the log in action

--
You received this message because you are subscribed to the Google Groups "LoopbackJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to loopbackjs+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mrinal Purohit]

A quick question, I have created a separate model customers that has a base of 'User'. Now I want that email should not be a mandatory field while registering a user. Only username should be. To do this, I defined customer.json as

{
    "name": "customers",
    "base": "User",
    "idInjection": true,
    "properties": {
        "NAME": {
            "type": "string",
            "required": false
        },
        "email":{
            "type":"string",
            "required":false
        },
        "username":{
            "type":"string",
            "required":false
        }

    },
    "validations": [],
    "relations": {},
    "acls": [],
    "methods": []
}

but not working!

[Brian Bagdasarian]

First, it looks like your json isn't quite correct Model Name. Should be customer.   Plural is customers.   Second,  make sure that the fields you are overriding are named properly (and the same) . Third,   what is in your js file for the model?

[Brian Bagdasarian]

One more thing...  How did you create the model?

[Mrinal Purohit]

I created two files inside common->models

1. customers.json (plurals fixed)

      { "name": "customer",

"base": "User",
"idInjection": true,
"properties": {

"email":{
"type":"string",
"required":false
},
"username":{
"type":"string",
"required":false
}

},
"validations": [],
"relations": {},
"acls": [],
"methods": []
}

2. customers.js

module.exports = function(customer){

}

And then i made the following entry in model-config.js

"customer": {
    "dataSource": "mango-database",
    "public": true
}

[Simon Ho]

See my new example repo at https://github.com/strongloop/loopback-faq-user-management

If you have any more questions beyond those, feel free to ask me again. ;)

[86tfv987]

Please check out a question about your exapmle https://github.com/strongloop/loopback-example-user-management/issues/26.

I also paste it here:

So you have this line in your example:

if (!req.accessToken) return res.sendStatus(401); 
link: https://github.com/strongloop/loopback-example-user-management/blob/master/server/boot/routes.js#L45

Ok, looks fine. But how do you push the accessToken into req so that the accessToken can be checked out that way?

In your login route I only see this. You only return the accessToken on the client:

      res.render('home', {
        email: req.body.email,
        accessToken: token.id
      });

link https://github.com/strongloop/loopback-example-user-management/blob/master/server/boot/routes.js#L36

And what does happen then? How the accessToken is a property of req, req.accessToken?