HttpOAuth2Connector is unable to identify the endpointId for root-path requests

[wabson]

This issue was discovered while investigating share-extras/myalfresco-dashlets#1 and occurs when a request is made to the root path of an endpoint via the proxy controller.

In these circumstances, the connector is not able to correctly identify the ID of the endpoint from the request, and therefore it is not possible to load any user tokens for that endpoint.

The following debug logs from share.log show this happenning

3:21:33,722 DEBUG [org.sharextras.webscripts.connector.HttpOAuth2Connector] No tokens found. Loading from tokenstore.
13:21:33,723 DEBUG [org.sharextras.webscripts.connector.HttpOAuth2Connector] Loading OAuth tokens for endpoint proxymyalfresco-api
13:21:33,723 DEBUG [org.sharextras.webscripts.connector.OAuth2CredentialVaultProvider] Generating key oAuth2CredentialVaultProvider
13:21:33,724 DEBUG [org.sharextras.webscripts.connector.OAuth2CredentialVaultProvider] Creating new credential vault with ID admin
13:21:33,767 DEBUG [org.sharextras.webscripts.connector.OAuth2CredentialVault] No tokens stored for endpoint proxymyalfresco-api
13:21:33,767 DEBUG [org.sharextras.webscripts.connector.OAuth2CredentialVault] Retrieving credentials
13:21:33,767 ERROR [org.sharextras.webscripts.connector.OAuth2CredentialVault] Could not locate user object in request context

In this case the endpoint ID was incorrectly returned as proxymyalfresco-api instead of myalfresco-api.