openqa login via openid redirects me to mirrorcache-eu.opensuse.org
Logging in to openqa.opensuse.org via OpenID instead logs me into mirrorcache-eu.opensuse.org, but not openqa.
#3 Updated by andriinikitin over 1 year ago
I blame ipsilon , because problem randomly raises for some period of time and then disappears, without any changes from mirrorcache side.
Moreover, today for me it did redirect to localhost when I tried to login to both openqa.o.o or mirrorcache.o.o
And a colleague of mine did share the same experience few days ago.
bmwiedemann is there chance you send me ipsilon logs for today, at least for andriinikitin log attempts and maybe meissner?
#4 Updated by andriinikitin over 1 year ago
Btw these are times (probably CET, but may be UTC) where login did misbehave:
#5 Updated by andriinikitin over 1 year ago
- Assignee changed from andriinikitin to bmwiedemann
Current known cases are (Where users try to log in -> where they are redirected):
- openqa.opensuse.org -> mirrorcache-eu.opensuse.org
- openqa.suse.de -> mirrorcache-eu.opensuse.org
- local instance of openqa -> mirrorcache-eu.opensuse.org
- local instance of mirrorcache -> openqa.opensuse.org
- local instance of mirrorcache -> localhost
- mirrorcache-eu.opensuse.org -> localhost
I was trying to debug log provided by Bernard and see a case with somebody's openqa instance, where the user gets a page containing:
[Fri Feb 19 10:30:01.977542 2021] [wsgi:error] [pid 29902] [remote 192.168.47.21:48512] <h4>You are being asked to login by http://sleposbuilder2.suse.cz/</h4>
and then get this confirmation about new provider for the same request:
[Fri Feb 19 10:30:19.594603 2021] [wsgi:error] [pid 29902] [remote 192.168.47.21:48958] <p>The OpenID relying party <b>https://mirrorcache-eu.opensuse.org/</b> is asking
I cannot imagine client's (mis)configuration which will result in such behavior.
I believe people more often land onto mirrorcache instance, because it sends requests to id.opensuse.org more often than necessary.
I am addressing this particular issue, so the problem should occur less frequently.
( https://github.com/andrii-suse/MirrorCache/pull/78 )
But I still think there is some concurrency issue at ipsilon side. Hopefully it will be less visible after my change.
#10 Updated by bmwiedemann about 1 year ago
- Status changed from New to Feedback
- % Done changed from 0 to 50
I moved our transactions sqlite DB to mariadb.
Also properly packaged up my custom patches from pagure.io/forks/bmwiedemann/ipsilon devel branch
and dist-upgraded to 15.2
The interesting question now is, if it keeps working when more mirrorcache logins happen again.
#13 Updated by andriinikitin 12 months ago
Just an observation - today me and a colleague see often an error 'time_bad_sig: Return_to signature is not valid.' when trying to login to mirrorcache-eu.opensuse.org and mirrorcache-us.opensuse.org .
It let me trough after several attempts.
For reference - example signature used: openid.return_to=https://mirrorcache-eu.opensuse.org/response?oic.time=1622111887-fc18d886a6853dcb5e9e&openid.sig=V8h1e66hDPlF4ygY0LPGAo2gFaI=
Both machines were updated to leap 15.3 recently(, not sure if that matters).