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
Describe the problem you would like to solve
Our institution prescribes login with MFA starting mid 2025.
The OpenID plugin is a welcome and good solution, and we would force authors/reviewers/editors/journal admins to use ORCID OpenID Connect as only login option.
However, there are functional accounts used for administering the site (e.g. add new journals, installation of plugins, ...) or testing the journal - these still require the legacy login.
In order that people not having functional access not to be able to legacy login page, this must disabled on {journal-URL}/login . However, for the functional accounts, a separate legacy login page needs still to be offered (only known to users that work with functional accounts).
Describe the solution you'd like
Configuration of having legacy login on a separate login path than {journal-URL}/login.
Who is asking for this feature?
Site administrators
The text was updated successfully, but these errors were encountered:
Describe the problem you would like to solve
Our institution prescribes login with MFA starting mid 2025.
The OpenID plugin is a welcome and good solution, and we would force authors/reviewers/editors/journal admins to use ORCID OpenID Connect as only login option.
However, there are functional accounts used for administering the site (e.g. add new journals, installation of plugins, ...) or testing the journal - these still require the legacy login.
In order that people not having functional access not to be able to legacy login page, this must disabled on {journal-URL}/login . However, for the functional accounts, a separate legacy login page needs still to be offered (only known to users that work with functional accounts).
Describe the solution you'd like
Configuration of having legacy login on a separate login path than {journal-URL}/login.
Who is asking for this feature?
Site administrators
The text was updated successfully, but these errors were encountered: