Looks like known issue on their side https://gitlab.com/gitlab-org/gitlab-ce/issues/29468 . Maybe instead of hardcode 1 second pause, we can rather poll their UserInfo endpoint in some periodic interval? Similar approach like the "Retry" class from our testsuite is using. Marek On 13/10/17 01:49, Bill Burke wrote: > Seems that Gitlab tokens take a little bit to propagate. Our GitLab > identity provider will get a 401 error when it calls the Gitlab user > info service intermittently. This is solved by putting in a 1 second > delay. Seems like a hack. Should we just not provide Gitlab social > login? > > Thanks, > > Bill > _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev