Re: Trouble enabling diego ssh in cf-release:222 diego:0.1437

Home Messages Hashtags Subgroups

Matthew Sykes <matthew.sykes@...> #2494 Does /v2/info contain the `app_ssh_auth_client` key? If not, it should be set to the client ID of the ssh proxy. If it's not set, I think that's one of the symptom. https://github.com/cloudfoundry-incubator/diego-release/blob/develop/stubs-for-cf-release/enable_diego_ssh_in_cf.yml#L4 toggle quoted message Show quoted text On Wed, Oct 28, 2015 at 7:36 PM, Mike Youngstrom <youngm(a)gmail.com> wrote: I'm working on upgrading to latest cf-release+diego and I'm having trouble getting ssh working. When attempting to ssh with the latest cli I get the error: "Authorization server did not redirect with one time code" The relevant config is: ssh_proxy.uaa_token_url=https://{uaa server}/oauth/token uaa.clients.ssh-proxy: authorized-grant-types: authorization_code autoapprove: true override: true redirect-uri: /login scope: openid,cloud_controller.read,cloud_controller.write secret: secret When tracing the CLI I see a call to "POST /oauth/token" and a 200. It appears that the CLI is expecting a redirect and not a 200. Is "oauth/token" the correct uaa_token_url endpoint? Any idea why UAA wouldn't be sending a redirect response from /oauth/token when the plugin is expecting it? Mike -- Matthew Sykes matthew.sykes(a)gmail.com attachment.html
More All Messages By This Member

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