can't login with google SSO "auth-error"

[Freundschaft]

Hello,

I have configured outline to run on my kubernetes cluster and things are looking good, but I can't login, because something fails during oauth login.

I always get redirected to this screen:

Is there a way how I can get debugging info on why passport fails?

I am running version-0.54.0

Cheers

[tommoor]

Errors should be in the server logs output from the Node proccess

[Freundschaft]

OK I fixed this now, Redis and S3 looking good, but still no luck authenticating. (logs attached)

outline-57c6844bf9-z6k6d_logs.txt

I can't help but think that this might not be related to S3 at all, but some issue with the Google SSO and passport itself.
authentication and user tables are still empty. Shouldn't I see some CREATE or UPDATE commands in the log at some point?

[andreipoe]

Hi!

I'm having the same issue you are having: authentication fails, but nothing is printed in the logs. I've gone through the discussion and my database in the same state yours was. As for the InvalidAccessKeyId errors, I've noticed these only show up on the first run, and I can use the same credentials in the browser. My SECRET_KEY and UTILS_SECRET variables are set as suggested (generated using openssl rand -hex 32).

Do you have any more suggestions or hints where I should be looking?

Thanks!

[tommoor]

• What version are you using?
• Is it the official docker image?
• Have you setup S3 compatible storage yet?
• Please double check for console errors, you might want to slim down the other logging by clearing the DEBUG env variable incase it's hidden amongst sql logs etc

[andreipoe]

Thanks for the quick response!

It's the latest official Docker image, so v0.54. Just like OP, I used the set-up described in the README and minio for S3-like storage. The storage works in the browser and through the CLI tool.

In the docker logs, there is very little output, and no errors at all. I've tried looking through some files in the container, but I couldn't find any more detailed logs. If you can tell me where to look, I'll dig through there and see if I find anything relevant.

[andreipoe]

Hello. I built a new Docker image based on the latest commit and I now saw an error in the logs when I tried to sign in: ValidationError [SequelizeValidationError]: Validation error: Validation isIn on language failed. It seems the issue was I had set DEFAULT_LANGUAGE=en_GB, but only en_US is supported. Once I reverted that, I was able to log in.

I still got an InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records in the logs, but that didn't prevent me from logging in.

[Freundschaft]

Just wanted to check in to let everyone know that I solved the issues, apparently there was an issue with SECRET_KEY and UTILS_SECRET not set correctly in my environment, leading to this error