Troubleshooting

Fixing sign-in problems

What to do when Google, Microsoft, GitHub, GitLab, or Atlassian sign-in fails.

Sign-in uses your identity provider (Google, Microsoft, GitHub, GitLab, or Atlassian). If it fails, OSTaaS shows a screen that says "Sign-in needs your attention" along with a reference ID. That ID is safe to share with support and helps us trace exactly what happened.

Your account is never changed by a failed sign-in.

The most common causes

"The redirect URI is not associated with this application"

This means the identity provider does not recognize the address it was asked to return you to. It is almost always a provider-side configuration detail, not something wrong with your account. Try again in a minute; if it persists, contact support with your reference ID.

"We're having trouble logging you in" (Microsoft)

Microsoft (Entra) is strict about the exact return address and the permissions requested. OSTaaS requests only your basic profile (openid, profile, email, and User.Read). If you belong to multiple Microsoft tenants, make sure you pick the account you intend to use OSTaaS with.

This usually means a cookie was blocked. Allow cookies for the OSTaaS domain, disable strict tracking-prevention for the site, and try again. Private/incognito windows often block the cookies sign-in needs.

A reliable retry sequence

Use the Try again button on the error screen.
If it fails again, note the reference ID.
Clear cookies for the OSTaaS domain, or try a normal (non-incognito) window.
Confirm you are choosing the correct account with your provider.
Still stuck? Contact support and include the reference ID.

What we can see

We can look up a failed attempt by reference ID and tell you which stage failed — the redirect, the provider's consent, or the return to OSTaaS — without ever seeing your password.