toggle quoted messageShow quoted text
Just for context, the VS extension was only this week open-sourced by HP
and put into the CF incubator.
I expect this issue is arising because the VS extension was developed to
run with HP Helion, which has followed its own evolutionary path from a
previous version of CF, and so it has not been tested against CF edge.
As the Foundation and HP work together to incubate this project in earnest,
we'll work through these support issues and get it working with current
versions of CF.
I expect these speed bumps will get addressed quickly, and so thanks in
advance for your patience.
On Thu, May 14, 2015 at 6:40 PM, Price, Jon <jon.price(a)intel.com> wrote:
We have been trying to use the visual studio extension from
https://github.com/cloudfoundry-incubator/cf-vs-extension but get an
error when logging in.
Unexpected character encountered while parsing value: <. Path “. Line 0
The error message in the uaa logs come from the filter called
BackwardsCompatibleTokenEndpointAuthenticationFilter in the uaa code:
[2015-05-14 20:26:41.209] uaa - 14916 [http-bio-8080-exec-9] .... DEBUG
--- BackwardsCompatibleTokenEndpointAuthenticationFilter: Authentication
request for failed:
client authentication found. Remember to put a filter upstream of the
[2015-05-14 20:26:41.211] uaa - 14916 [http-bio-8080-exec-9] .... DEBUG
--- DefaultOAuth2ExceptionRenderer: Written [error="unauthorized",
error_description="No client authentication found. Remember to put a filter
upstream of the TokenEndpointAuthenticationFilter."] as "application/json"
Has anyone else tried the cf-vs-extention on their private CF environments
and have you seen this problem?
cf-dev mailing list