This is a good solution in so far as it may be easier for the subscriber to provide strong authentication for its users, using existing authentication schemes. For example, this library uses the barcode and PIN from its library system. Use of LDAP would also be possible as this is already in place for email access. The major drawback with this method is that it is not yet widely accepted. Where authentication is by login, local users generate an administrative burden in so far as login details must be distributed and records maintained.
Remote users are more difficult.
If the provider uses IP authentication only, then remote users are effectively excluded, since it would be impossible to define IP ranges to cover all the possible ISP accounts which remote users might use. If the provider offers authentication by login, remote access becomes possible, but again the library is faced with the burdens already discussed for that method. In-house use has additional challenges, in so far as the library is open to the public. This approach has been used successfully with FirstSearch and some other databases. Unfortunately, some providers use non-standard login methodologies which preclude local scripting.