I am still can not solve this problem.
how I can by pass the log in form in admin and go directly to admin site.
Here is my goal:
User access admin site using Cosign.
User Enter pass and user name and it is verify by cosign then he go directly to admin site without pass by login form to enter the user name and password.
Here is what I did so far:
1- creating a plugin that includes a log in_adapter filter. And creating a an object called xxx implement interface adapter, that include a constructor to receive the user name and authorization method that will verify that the user name in the db in Omeka to gave success result.
The class works good and I do receive success message that the user grated authorization to access the site. but still the login form show up every time and i have to enter any thing in the user name and password field and click on submit.
do I need to create a controller class that implement an Log in Action function? I saw a user class which extend a controller class include a log in action function that initiate the call for the form.
Unfortunately, Omeka doesn't have that functionality integrated into the application.
I believe one other project created a plugin that allowed for LDap user authentication, they did not by-pass the admin login page. It is not possible to get rid of the admin login page.
I looked at LDAP plugin in, it is still use the login page and ask the user to enter the user name then verify it against the LDAP.
However, if it is for sure we can not pass the login in form, how about passing the user name I received from Cosign form to the Omeka user name in login form and somehow post the login submit button without asking the user to do these steps again? is that possible and how I can achieve this?
I want to avoid asking the user to enter user name and click on submit button again?
This isn't something that we support, so we really can't answer your questions about this issue. We pointed to you to the one alternative login authentication plugin we know of using LDAP built by another developer.
We do encourage you to play around with the code and if you do find a way around this, please share it back with the community.