Hi all,
I'm at my wit's end in looking for solutions to be able to login to my Atlassian products again. We make use of the cloud offerings, and use our microsoft accounts for login.
When I'm in one location, my ubuntu laptop refuses to log in, and the auth.atlassian.com/login/callback?connection=saml.... always results in a 502 Bad gateway error. Same with an incognito window.
I'm sure the problem is local to the laptop, but I have no idea where to look for this issue. All my colleagues in the same location have no login issues, and I'm typing this on my macbook, on the same network.
I've completely removed chromium, and installed Google chrome, no extensions, and still the problem persists, Laptop is up to date with all latest updates. No entries in the hosts file.
I really hope someone out there have some idea/guidance, as the next step is to format and reinstall, something I'm not too keen on.
Thomas
Hi @thomas ,
Welcome to the Atlassian Community!
Right now, we have two options to log in through the Microsoft authentication: using SAML through Atlassian Access with Azure AD or using the Social Login by selecting the toption.
Can you kindly confirm you are using the latter one (or provide more details)?
Also, please let us know the following:
Cheers,
Dario
Hi Dario,
1.) logging using the same account works on my mac. It also works on the ubuntu laptop when using a VPN connection or at home. That's the strange part - the issue with the atlassian products occurs only on the one network on this laptop. Hence the suspicion that it is tied to the combination device/network
2.) When not on the VPN, start.atlassian.com gives the same result - not being able to log in.
3.) Firefox - same issue
4.) Developer tools gives me nothing to work with
5.) see 1.
Regards
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @thomas ,
So, if I understand correctly:
Can you confirm?
If that's the case it can have to do with the way the office network is configured and it could be a good idea to get in touch with your IT department.
A thing you can try in your own is to set static DNS to exclude the possibility there is something wrong with the ones obtained automatically when connecting to that specific network.
If nothing works you can generate a HAR file when getting the error and ask your site-administrator to log a support request in https://support.atlassian.com/contact attaching the HAR file it.
Have a nice weekend.
Dario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.