I don't think it will be only a proxy, because we also need to store an encrypted cookie remember? To implement the auto-login, because we store the user access token of openwisp/django-rest-framework in an encrypted cookie and with that we determine if the user is already logged in or not and if not we can try to automatically log them in.
That said, if you find a solution that allows to solve specific problems like requests proxied to other services with few lines of code, please propose so we can evaluate. Fed On Fri, Apr 5, 2019 at 1:18 AM Vivek Rajput <[email protected]> wrote: > Hi Federico, > I have a doubt on this point mentioned in the ideas list. > > - The software shall provide a backend part implemented in Node.js, > which also serves as a proxy for all asynchronous (a.k.a. Ajax) HTTP > requests that need to be made to external services (obtaining auth token, > sign up, etc.); a configurable time-out should be set for all the external > requests, defaulting to 2 seconds and the failure scenarios should be > handled by displaying a nice error message to the user > > Does this backend serve any other purpose than proxying the Ajax requests? > If it's just a proxy server, then we can use any npm proxy server package > and configure it. > > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
