You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It currently seems to be impossible to login into https://stg.release-monitoring.org/ using a custom OpenID provider: after providing the OpenID URL on the login page, I am redirected to the same page again without being logged in. In comparison, on https://release-monitoring.org/login, I am first redirected to my OpenID provider to provide username and password, after which I am successfully logged in into Anitya.
I do not know whether login into staging might be disabled on purpose, but login using FAS or Yahoo (directly with the corresponding link on the login page instead of using OpenID) seems to work, at least it redirects to the provider login page (I cannot test further, as I do not have an account on one of these services).
The text was updated successfully, but these errors were encountered:
It currently seems to be impossible to login into https://stg.release-monitoring.org/ using a custom OpenID provider: after providing the OpenID URL on the login page, I am redirected to the same page again without being logged in. In comparison, on https://release-monitoring.org/login, I am first redirected to my OpenID provider to provide username and password, after which I am successfully logged in into Anitya.
I tried different browsers (Firefox, Chromium) and different OpenID providers (https://launchpad.net/~userid, https://openid.stackexchange.com, with and without the
https://
). Even Fedora and Yahoo OpenID (https://userid.id.fedoraproject.org/, https://me.yahoo.com) do not work, so I do not think this is a provider-specific problem.I do not know whether login into staging might be disabled on purpose, but login using FAS or Yahoo (directly with the corresponding link on the login page instead of using OpenID) seems to work, at least it redirects to the provider login page (I cannot test further, as I do not have an account on one of these services).
The text was updated successfully, but these errors were encountered: