Gitlab as openidc provider for AWS Cognito
Summary
GitLab returns error 502 when used as a openidc provider for AWS Cognito. If you are already logged in to GitLab and try to authenticate in Cognito, everything works fine.
Steps to reproduce
Cognito authentication page -> GitLab user/pass auth page -> GitLab 2FA ->Error 502
What is the current bug behavior?
Not sure that the openidc related settings are being passed between GitLab user/pass auth page and the GitLab 2FA page. Also, when I do the whole authentication process, which finishes with the "Whoops, GitLab is taking too much time to respond." page, even though I provided correct user/pass/2fa, I am still not logged in.
What is the expected correct behavior?
oidc data is passed to Cognito
Relevant logs and/or screenshots
Request URL passed to GitLab: https:/domain.auth.zone.amazoncognito.com/login?client_id=clientid&redirect_uri=application/oauth2/idpresponse&response_type=code&scope=openid&state=<state_hash>
Possible fixes
Pre-login to GitLab prior to accessing the Cognito authentication page