Auth error 500 identity-server

Support
1

I have…

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [ x ] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

Can`t login. Getting Error 500 on production when users is trying to login via google auth after return from confirm on google form. Locally all is fine.

Expected behavior

Successful auth

Minimal reproduction of the problem

Self docker hosting. Login via google auth on production with own google credentials.

Environment

  • [ x ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ ] Cloud version

Version: 5.8.2

Browser:

  • [ x ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

Others:
Use Cloudflare SSL. Locally authentication works but on production it returned error 500 wher redirected back from google form auth. Return Urls is checked.
Return Urls on google console:
http://some-host.com/identity-server/signin-google
https://localhost:5001/identity-server/signin-google

2

logs, dockerfile
image taking from bitbucket

3

Screenshot_3
Screenshot_31816×854 111 KB

4

Check your base url config and ensure that it is set to https.

5

base url config in appsettings it is https

6

I am not sure where I have seen it, but somehow Google is redirecting to http.

It is definitely a https / cookie issue. You can find it in the logs.

7

Google prod link is http://
When I set https:// it give me the error uri_mismatch. When I set http:// it redirects to app and app redirect request to https://. You can see it in the image above.
I haven’t changed anything else
baseUrl in appsettings is https:// always

8

But something is obviously wrong with the redirects. You have to dig into this.

9

See something. As I understand the app “says” to Google use http. It`s on a production. Somehow the app send redirect_uri with http
appsetting: “baseUrl”: “https://************”,

enter1
enter11876×899 260 KB
signR1
signR11823×869 297 KB
signR2
signR21826×865 215 KB

10

It`s local

Screenshot_11
Screenshot_111791×941 149 KB

11

Perhaps your proxy does not set the X-Proto-Forward header ?

12

Gave it to the devops. He check it out. I will write by the result
There is one more thing. I installed the Mozilla browser and tried to login.
It`s works.
I cannot enter through chrome and opera, but through mozilla I can.
I cleared the cache and tried it in incognito mode too. It does not work in chrome and opera. What could it be? I can’t understand what I’m missing

13

X-Proto-Forward is set

14

Then I have no idea right now.

I also have a setup with cloudflare and no issues. This should not be the problem.

15

Solved with set MinimumSameSitePolicy = SameSiteMode.Lax
Was Unspecified.

16

What kind of setting is this?

17

CookiePolicyOptions