GitLab SSO, infinite loop. SAML

By: Daniel ddd user 14 Nov 2018 at 9:06 a.m. CST

1 Response
Daniel ddd gravatar
Hello, I have installed gluu and configured to provide Single Sign On to some servers (Moodle and GitLab). The moodle ones work fine, with SSO and everything is perfect. The problem is that when I try to login through GitLab, the platform falls down into a infinite loop: asking https://MY-GLUU/idp/profile/SAML2/Redirect/SSO?SAMLRequest=**<SAML-REQUEST>** and making new GET queries every two seconds changing the SAMLREQUEST. So, the platform is not able to provide SSO to GitLab. I followed the official guides of GitLab Omniauth https://docs.gitlab.com/ee/integration/saml.html I have interchanged the metadata files between SP and IDP, and the IDP releases the following variables: Display Name, Email, First Name, Last Name, Nickname, Username. Thanks!!!
CentOS 7.0
closed

Answers

By Aliaksandr Samuseu staff 18 Nov 2018 at 8:28 p.m. CST

Copy
Aliaksandr Samuseu gravatar
Hi, Daniel. You havent provided enough details for us to be able to assist you. 1. Disable encryption for this Trust Relationship (we need to see all attributes passed in SAML response) 2. Capture the actual content of SAML request and response. There are a lot of options for this, like exporting network trace in a [HAR file](https://www.inflectra.com/support/knowledgebase/kb254.aspx) from a browser, or using [a plugin](https://chrome.google.com/webstore/detail/saml-chrome-panel/paijfdbeoenhembfhkhllainmocckace) 3. Provide us screenshots of your TR's pages with all settings you chose visible 4. Share SP's metadata you used to create this TR

Post an answer