Passport.js integration

Cheese · August 2, 2024, 12:14pm

Patrick recently replied regarding Passport JS integration in to Wappler, the response is below:

Back-end for Android Application, can't use Node?

The main problem with the passport integration is that it can't be integrated with serverconnect app instance. The serverconnect app instance is initialized on the route handler and is per request an other instance. The passport middleware runs before the serverconnect app is initialized and also has no access to any of its functionality.

As you notice in the documentation for example the passport-auth-token . You will need to program a part yourself, it only passes the authtoken to the callback function where you then have your own program logic and here we will not have access to serverconnect data or database connections.

The serverconnect app was originally not developed for NodeJS, the first version were for PHP and ASP. Later it was ported to NodeJS and kept fully compatible with the other versions. We have the advantage that we have full control over the server with NodeJS, but also the disadvantage that the code is based on PHP/ASP with its per request instance.

Middleware in NodeJS that do not depend on App logic (database connections etc) can be used without problem. Most of the passport middleware require you to have some app logic (like lookup user or token in a database) and without access to serverconnect instance at that moment it will require custom JavaScript coding.

I would have setup serverconnect for NodeJS differently now so that it would make use of the full functionality, but then it would be totally different from PHP/ASP. The filosofie of Wappler is that it should not matter which server model you use, they should all behave exactly the same.