![]() Processing by SessionsController#new as HTMLįilter chain halted as :require_no_authentication rendered or redirectedĬompleted 302 Found in 6ms (ActiveRecord: 1.8ms)Ĭompleted 401 Unauthorized in 6ms (ActiveRecord: 2.8ms)Ĭompleted 401 Unauthorized in 5ms (ActiveRecord: 2.3ms)Ĭompleted 302 Found in 7ms (ActiveRecord: 1.9ms)Ĭompleted 302 Found in 5ms (ActiveRecord: 0.9ms)Ĭompleted 401 Unauthorized in 3ms (ActiveRecord: 1.2ms)Ĭompleted 302 Found in 5ms (ActiveRecord: 1. Processing by RootController#index as HTMLĬompleted 401 Unauthorized in 7ms (ActiveRecord: 4.3ms) My first suspicion was redis, which has never been used before and which is managing the sessions. The redirect problem is affecting the login part only, as much as I realized. SSLCertificateFile /etc/apache2/mycert/server.crtĪnd the log at /var/log/gitlab/gitlab-rails/production.log tells me this: Filter chain halted as :require_no_authentication rendered or redirectedĬompleted 302 Found in 7ms (ActiveRecord: 2.0ms) /index.php/apps/files shows the appropriate page and all the further navigation works as usual. SSLCertificateKeyFile /etc/apache2/mycert/server.key ProxyPass / ProxyPassReverse / SSLEngine on RequestHeader set X-Forwarded-Proto "https" My Apache 2.4 vHost is configured like this: ĮrrorLog /var/log/apache2/ Unicorn = 8890 # needed, since the port 8080 was already in use I did some changes in /etc/gitlab/gitlab.rb: external_url '' I tried every solution I found until now, but none of them are working for me. So far I can see the login page and browse around, but when I try to login using the default username and password I end up in an infinite loop of redirects and I can't find the reason why. Then I configured it to use the external domain (changed for security reasons) and I want to proxy it via Apache using a reverse proxy with SSL. I installed it on Ubuntu 14.04 by using the available packages from the Gitlab site at: I'll get back to u shortly.Since yesterday I'm trying to install Gitlab on my homeserver, but so far I haven't had any luck in getting it running :( I'll set up a standalone test app on my default directory (trusted pub domain) and see if I can get it to break the way that your app is breaking. and cross-link "untrusted publisher domain" to the Azure doc on that. Say in Step 4 that if working with an untrusted publisher domain to uncheck that Permissions checkbox.Write out that the dev should navigate to Azure Active Directory.so I know two more things that I need to do on the PR. I discovered this by switching directories to my default directory and then going to the app registration page. The delta is that your publisher domain is trusted, and I've been working from an untrusted publisher domain. PROBLEM: There is an issue with how the default.aspx page is redirecting to the SAML authentication method. WRT to the app registration screen and Step 4's instruction generally. The infinite redirects can be validated within the IIS logs and from a browser network capture as shown below. My app registration screen opens with it checked. I'll make it say something more specific on the open PR. Yes, it's the "Azure Active Directory" part. Show a screenshot (with sensitive data removed).Īzure Active Directory > App registrations If you're not seeing the setting in your app registrations area of AAD, I know someone we can ping on the Azure docs side to comment on it. ![]() can you take a screenshot of what you're seeing and indicate where in the portal you're at (what path of screens did you follow to get the new app registration screen to load)? Azure does toss up test UIs in A-B testing from time-to-time and can have other peculiarities that sometimes display different content/values to users. Here's the new app registration screen from the portal marking the setting for Step 4. your character is tested in a Star Trek Kobayashi Maru! □ The whole config is very sensitive to any little thing being off. I recommend that you compare your app and Azure config to what the topic shows section-by-section and re-walk the Azure portal steps at the top. Usually, these sorts of problems end up being a configuration problem in the app or in the Azure portal config. ![]()
0 Comments
Leave a Reply. |