server-nodejs : authenticate users using a remote server

[axl-pis]

For now, we authenticate users on the local server using the local database. We would like to be able to configure the local server to delegate the authentication process to another damas-core server.

[remyla]

the jwt-delegate doesn't properly work and needs debug :\ This extension is needed in SyncPlanet service with some improvements that could be made (would explain more in further message) Re-opening the issue! @axl-pis

[remyla]

By extension, how the different errors will be processed?

the server could return a 401 or 200 (https://github.com/remyla/damas-core/wiki/4-Specifications#signin)

• upon 200: we copy the user node returned by the server and store it locally
• upon 401: we could not authenticate the user. The user can be disabled, unknown, or a wrong password was specified. What process could we do ? erase the user if it exists? mark it?
• upon server not found: authenticate with a local signIn

[remyla]

I write a bit more details about how the delegated authentication could work.

• 1. the user wants to authenticate on server1 using the /api/signIn method (like usual, nothing is changed from the user point of view)
• 2. the server1 has the jwt_delegate extension loaded. Instead of directly responding to the /api/signIn call like usual, he will make a call to another server, the delegation server (server2, which address is configured in the configuration file) to retrieve the user node if possible
• 3. after processing the possible errors (server not found, invalid user, response does not contain user) the server1 will store the user node locally to allow a local authentication.
• 4. the jwt extension can now process the /api/signIn call using its local database without code modification