For the benefit of others it appears we have solved our problem by setting HTTP authentication on the templates we are using.
Do this via Design->Template preferences, select the template and set HTTP authentication to 'yes' (the option at the bottom of the form).
This uses HTTP authentication against the EE member credentials stored in the database and ...
I would suggest building a simple API module within the EE installation.
You've found the Auth library which should do exactly what you need, it's just a matter of exposing it, because there really isn't an easy way to take EE's authentication scheme out of EE.
So once you create a module, it'd simply be a matter of setting up an action ID within the ...
I don't think there is currently an add-on that would allow "login as member" functionality from the front-end (e.g. any other place then the EE control panel)
However you could write (or commission to let write) a small plugin, based on the login_as_member() and do_login_as_member() functions. As a starting point for development see this question about ...
Nothing comes to mind for a plugin specifically, but this is more of a job for the .htaccess file to handle. If you aren't familiar with all of the rules to apply, there is a great book available - http://htaccessbook.com
There's a few ways to approach this, the following is by no means providing perfect examples but just indicating the possibilities ...
I've had to build a member importer for a client's website in which I did the same thing you're thinking about doing: inserting a member directly into the database.
As long as you add all of the fields that are required, you are good to go. Just look up the EE way of adding members and duplicate that.
Just don't forget about the exp_member_data and ...
EE doesn't have a native API interface to communicate with, but I've been having quite a good time with Webservice API plugin from Reinos, and with it you can turn a EE install into a REST/XMLRPC/SOAP server. They've also done the hard work of connecting with many third-party add-ons. Check out the docs here.
Almost two years later there is a response from the Expression Engine support team:
The above method is for HTTP Auth access control of a template, when enabled
in a template’s settings. This optional feature uses an appropriate solution
when PHP is given the task of providing this functionality. ref:
If you look in the EE source (v.2.10.1) you will see the following in system/expressionengine/libraries/Auth.php (line numbers on the left):
156 if ($authed === FALSE)
158 @header('WWW-Authenticate: Basic realm="'.$realm.'"');
Take a look at Protected Links. This will allow you to limit link usage by IP, Member group, Member ID as well as hotlinking protection (and more I think!)
You can also create links via the CP or have it generate links on-the-fly.
You didn't mention your EE version but sounds like it might be this bug:
Instead of logging in with "http://www.url.net/admin.php", try using "http://www.url.net/system" instead... NOTE: "system" should be changed to whatever you renamed your system directory if you renamed it.
OR update to the most recent ...