It would be nice to not redirect the user to OAuth2Controller as soon as they click on the Log in link, but show the usual login page with an extra button for the OAuth2 authentication, or keep two different Log in links, one for OAuth2 users, one for CKAN users. That would allow existing users to log in.
It would be nice to not redirect the user to
OAuth2Controlleras soon as they click on theLog inlink, but show the usual login page with an extra button for the OAuth2 authentication, or keep two differentLog inlinks, one for OAuth2 users, one for CKAN users. That would allow existing users to log in.https://github.com/conwetlab/ckanext-oauth2/blob/e68dd2664229b7563d77b2c8fc869fe57b747c88/ckanext/oauth2/plugin.py#L102-L104
We could have an option just to map such controller to a different URL, so that it does not override the original one. Any opinion on that?