Optionally pass accessToken as a parameter to returnTo

[gausie]

On mobile devices, it is useful to have the login redirect to a URL with a custom protocol (myapp://) so that the intent can be captured and the login processed. In 1.6.0 we have the ability to set a returnTo session key for the successRedirect.

It would be extremely useful to be able to append the accessToken generated from a successful login to this URL as query parameters, as they can be read by a mobile application.

[jonathan-casarrubias]

when you configure the passport provider you set the success url, set that as a middleware in the backend like

"successRedirect": "/auth/account"

then just create a middleware like

app.get('/auth/account', function (req, res, next) {
        app.models.Account.findById(req.accessToken.userId, function(err, account) {
            if (err) { next(err); }
            res.redirect('http://yourdomain.com?accessToken=' + req.accessToken.id + '&userId=' + account.id);
        });
    });

[anupvarghese]

Thanks @jonathan-casarrubias this is a good suggestion.

This looks like a good option for SPA login. I am using it as below in my react client app,
Login.jsx

import React from 'react';
class Login extends React.Component {
render() {
    const googleLogin = () => {
      window.open('http://localhost:3000/auth/google'); // Do some modifications for window close on successful login or cancel clicks
  };
}
return (
  <div>
    ........
    <a href="#" onClick={googleLogin}>Google +</a>
  <div>
  );
}

at server.js in loopback app

app.get('/auth/account', function(req, res, next) {
  console.log(req.accessToken);
  //res.json(req.accessToken);
  res.redirect(301,'http://localhost:8080/dashboard?accessToken=' + req.accessToken.id);
});

Is it possible to create a middleware in the failure case also?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.