Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log in Azure Active Directory link leads to 404 Page not found error page #45

Open
markusleino opened this issue Aug 30, 2019 · 3 comments

Comments

@markusleino
Copy link

When pressing Log in Azure Active Directory link in TeamCity login screen you get error page "404 The page is not found". Reason seems to be wrong URL. It points to TeamCity server instead of Microsoft login page. If you replace TeamCity server address with Microsoft login page address and keep rest of the URL same it works fine.

Plugin version is SNAPSHOT-20180516102618

@opernes
Copy link

opernes commented Dec 11, 2019

Same issue here, trying to open a case at jetbrains and will follow up here

@laurencee
Copy link

laurencee commented Jan 20, 2020

Yep same issue just starting occuring for us as well a few days ago

I should add that I "fixed" this for us by hardcoding a rewrite rule in our IIS reverse proxy to specially treat that URL value:

<rule name="oauth fix" stopProcessing="true">
  <match url="^my-guid-here/oauth2/authorize(.*)" />
  <action type="Redirect" url="https://login.microsoftonline.com/my-guid-here/oauth2/authorize{R:1}" />
</rule>

@laurencee
Copy link

laurencee commented Jan 28, 2020

Ok I eventually figured out the actual cause of this for us, the problem was our IIS Reverse Proxy had Reverse rewrite host in response headers option enabled by someone in ARR.

After disabling that the redirect worked as expected so I'm guessing something similar is going on here for others where response header host values are being incorrectly rewritten.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants