Google Login challenges
-
I closely followed the instructions to set up Google Login, but after setting variables and restarting the app still see an
invalid-authentication
error upon logging in. Interested to hear if others have had success with this.{ "error":"Validation error", "level":"error", "message":"Error during authentication", "stack":"UnauthorizedError: Validation error at InvalidAuthenticationError (/app/code/build/server/errors.js:46:34) at accountProvisioner (/app/code/build/server/commands/accountProvisioner.js:59:54) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)" }
-
Thanks. Question posted upstream (https://github.com/outline/outline/discussions/6130)
-
Guys, I hate to say this, but this sort of problem has long been a hurdle to self-hosting Outline. The effort and focus that went into getting it ready to Cloudron is admirable and laudable, but I don't have high hopes that enough people are going to find this useful and usable.
-
I wanted to post an update on this based on this response to my post on the Outline repo...
The
authentication_providers
database record for Cloudron OIDC and for Google Login need the sameproviderId
value (i.e., email domain), but only one can have it set.I confirmed that if a fresh Outline installation specifies that account management should be left up to the application does work properly with Google Login (assuming
GOOGLE_CLIENT_ID
andGOOGLE_CLIENT_SECRET
are set in env.sh file.)Ideally, Cloudron login and Google Login options would co-exist, but this isn't strictly necessary in our case.