OSLCServer connect() and use() are jazz.net app specific

[jamsden]

OSLCServer currently uses jazz.net specific login on connect() and jazz.net rootservices on use(). These could be made more generic. OSLC core does not mandate an authentication mechanism (but recommends Basic or OAuth/OpenID), nor does OSLC core specify how discovery is discovered. So it is not unusual for these two capabilities to be application specific.

However, some mechanism should be supported that is more open. Perhaps a separate login() function could be added to support Basic authentication. Or connect() could have an additional function argument to use for login.

Instead of rootservices, use() could take a URI to a specific ServiceProviderCatalog and use that directly.

[jamsden]

Also request.js does not support JEE Form authentication and isn't browser friendly - it doesn't rely on the browser to deal with authentication challenges.

Perhaps axios or SuperAgent might be better options.

Another option would be to figure out how to register request and/or response receptors in request.js and implement JEE Form authentication there.

[berezovskyi]

@jamsden thanks for the 3.0.1 release! Is this issue still relevant?