https://i.imgur.com/ekJg7XW.png
Balanced auth api (for user management) doesn't use api keys like the regular endpoint, but instead uses session id's from a cookie. I believe these expire every time a new login happens for the user who generated it. We need a way to renew the session.
We could create a new Balanced user with minimal access, just read access to users. Provided no one uses this user to login via the web, we could just use their session id, and that would be a quick fix. To actually solve the issue, we should use something like mechanize to programmatically login with this user when needed and piggyback on that session. we'd then be storing the username and password for that dummy user as envvars.
cc: @clone1018
https://i.imgur.com/ekJg7XW.png
Balanced auth api (for user management) doesn't use api keys like the regular endpoint, but instead uses session id's from a cookie. I believe these expire every time a new login happens for the user who generated it. We need a way to renew the session.
We could create a new Balanced user with minimal access, just read access to users. Provided no one uses this user to login via the web, we could just use their session id, and that would be a quick fix. To actually solve the issue, we should use something like mechanize to programmatically login with this user when needed and piggyback on that session. we'd then be storing the username and password for that dummy user as envvars.
cc: @clone1018