Re: can't login with cf CLI but the UAAC tool works


Filip Hanik
 

Turn on trace, and post your data here. remember, if this is a prod
environment, you may want to send me the token directly
We can show you how to decode this token, and see why it is invalid.

Filip

On Fri, Sep 4, 2015 at 11:59 AM, kyle havlovitz <kylehav(a)gmail.com> wrote:

I'm having an issue with my cloud controller/UAA setup where when I do cf
login I get '401 unauthorized' back, but when I use the uaac command line
tool to get a token it works fine. This makes me think the UAA is working
but something is off with the cloud controller config, but I'm not sure
what. The only strange thing I see is that the CLI is POSTing to
/oauth/token and the uaac goes to /oauth/authorize.

This is all using v215 of cloudfoundry running/built locally and 6.12.3 of
the cli. Is there some endpoint that needs to be set correctly in the cloud
controller config?


Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.