Google Login challenges

[sparkwise]

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)"
}

[girish]

I have to say the main error and subtext of the error does not match. It says authentication failed but the explanation seems like authorization failed (but authentication succeeded). Maybe you can ask upstream what this error means?

[sparkwise]

Thanks. Question posted upstream (https://github.com/outline/outline/discussions/6130)

[scooke]

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.

[girish]

@scooke atm, it works well with Cloudron OIDC. I do agree that making it work with Google SSO can be quite a stretch though.

[girish]

@scooke Spoke too soon Already have a bug in our first update - https://github.com/outline/outline/issues/6153

[sparkwise]

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 same providerId 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 and GOOGLE_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.

[girish]

@sparkwise strange.. the oidc and google variables should not interfere with each other

[marylou]

Unfortunately, I can confirm that Cloudron and Google logins cannot co-exist.

[sparkwise]

@marylou Where we ended up landing: both buttons are visible but only Google Login button gets used. Not perfect, but the app is fantastic.