On Tuesday, April 9, 2019 at 12:51:52 AM UTC-4, Vivek Chand wrote: > > Hi Fed > I created this demo of my prototype for the project proposal. > https://www.youtube.com/watch?v=g3QipLOGmjg > Please have a look at it. > > Will do as soon as possible.
Also, I have successfully made a node.js proxy API endpoint for the login > feature which listens for the requests at /api/v1/login and makes requests > to the actual URL. > Good! > I also implemented the feature to set a signed cookie. But to sign a > cookie a secret phrase is required and I have a doubt regarding that. I > want to clarify if a single secret phrase will be used for signing cookies > of all the organization or different phrase for different org or different > for different users. If we are to use different phrases for different > organizations than either we need to make changes to openwisp_radius and > create another api endpoint to get this phrase, or we'll have to integrate > MongoDB or NoSQL with the node.js backend and randomly generate these > phrases for different organizations or users and store them in the node > database. Please guide me on this. > That's something like the secret key that django has. Django uses just one for everything, so maybe we can do the same, since each organization won't know what the secret key is, because usually it won't be them setting up the application, but the sysadmins. The application will not have its own database, the max we can do is to keep in mind that one day the configuration of the application may be taken from an API endpoint in OpenWISP rather than a file (or a series of files like you're doing now). F. -- 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.
