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

Follow requested URL after login #42

Open
SithVicious opened this issue Nov 13, 2018 · 5 comments
Open

Follow requested URL after login #42

SithVicious opened this issue Nov 13, 2018 · 5 comments

Comments

@SithVicious
Copy link

When using Built-in teamcity authentication, a user who requests a different page such as /queue.html will be prompted to login, and then redirected to /queue.html.

With Azure AD plugin this does not happen, users are always directed to /overview.html after logging in using Azure AD.

@nejoyer
Copy link

nejoyer commented Jan 18, 2019

This is a major pain point to me. I'm always following deep links and so ending up on /overview is not helpful. This wouldn't be a big deal if I was able to stay logged in longer, but it seems I'm logged out multiple times per day.

@tolache
Copy link
Contributor

tolache commented May 6, 2022

From a support request:

We make heavy use of the Slack Notifier, and folks often times get confused when they click a link to a specific build, and end up at the main TeamCity overview page after logging in via AAD. We noticed in testing the ADO plugin properly redirects back to the specific build link in these same situations.

@werner-kapferer-lgs
Copy link

Does it make sense to ping this issue in 2023?
If yes: ping 😄

@galvesribeiro
Copy link

Another ping from the future...

@galvesribeiro
Copy link

I found a way to get it work. Check my comments here. As long as your active browser is authenticated in AAD AND you had open TeamCity pages at least one (I guess to make sure the TC auth cookie is set), it will work.

All links from Slack will go to the correct place instead of redirecting to home.

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

No branches or pull requests

6 participants