Cloud foundry Can';t使用cf命令登录
在将目标设置为api.cloudfoundry.com之后,我无法通过“cf login”登录 我对我的凭据很确定,因为我可以登录login.cloudfoundry.com 可能与新版本有关吗 我已经看到,有些时候你要求Cloud foundry Can';t使用cf命令登录,cloud-foundry,Cloud Foundry,在将目标设置为api.cloudfoundry.com之后,我无法通过“cf login”登录 我对我的凭据很确定,因为我可以登录login.cloudfoundry.com 可能与新版本有关吗 我已经看到,有些时候你要求cf login-t输出,所以,这是我的: 更改****** Authenticating. ---> request: post https://uaa.cloudfoundry.com/oauth/token headers: content-typeapplica
cf login-t输出
,所以,这是我的:
更改******
Authenticating. --->
request: post https://uaa.cloudfoundry.com/oauth/token
headers: content-typeapplication/x-www-form-urlencoded;charset=utf-8acceptapplication/json;charset=utf-8authorizationBasic Y2Y6
body: grant_type=password&username=bertyno%40yahoo.es&password=******
...<---
response: 401
headers: content-typeapplication/json;charset=utf-8servernginxkeep-alivetimeout=20dateMon, 13 May 2013 12:19:13 GMTtransfer-encodingchunkedwww-authenticateBasic realm="UAA/client", error="unauthorized", error_description="No client with requested id: cf"cache-controlno-storeconnectionclose
body: {"error":"unauthorized","error_description":"No client with requested id: cf"}
--->
request: post https://uaa.cloudfoundry.com/oauth/authorize?redirect_uri=https%3A%2F%2Fuaa.cloudfoundry.com%2Fredirect%2Fcf&client_id=cf&response_type=token&state=2b7fbfd964323e8c639da0157c00435b
headers: content-typeapplication/x-www-form-urlencoded;charset=utf-8acceptapplication/json;charset=utf-8
body: username=bertyno%40yahoo.es&password=******&source=credentials
...<---
response: 401
headers: pragmano-cache, no-cachecontent-languageen-UScontent-typeapplication/json;charset=UTF-8servernginxkeep-alivetimeout=20dateMon, 13 May 2013 12:19:14 GMTtransfer-encodingchunkedcache-controlno-cache, no-store, no-cache, no-store, max-age=0expiresThu, 01 Jan 1970 00:00:00 GMT, Thu, 01 Jan 1970 00:00:00 GMTconnectionclose
body: {"error":"invalid_client","error_description":"Bad client credentials"}
... FAILED
验证。-->
请求:邮寄https://uaa.cloudfoundry.com/oauth/token
标题:content-typeapplication/x-www-form-urlencoded;charset=utf-8AcceptationApplication/json;字符集=utf-8授权基本Y2Y6
正文:grant_type=password&username=bertyno%40yahoo.es&password=******
...
请求:邮寄https://uaa.cloudfoundry.com/oauth/authorize?redirect_uri=https%3A%2F%2Fuaa.cloudfoundry.com%2Fredirect%2Fcf&client_id=cf&response_type=token&state=2b7fbfd964323e8c639da0157c00435b
标题:content-typeapplication/x-www-form-urlencoded;charset=utf-8AcceptationApplication/json;字符集=utf-8
正文:username=bertyno%40yahoo.es&password=******&source=credentials
Cloudfoundry.com给我发了一封关于Cloudfoundry v2发布的电子邮件(6月5日):
CloudFoundry.com V2将于6月10日左右提供
您可以在中查看cloudfoundry.com支持的当前API
cloudfoundry v1中的应用不会自动迁移到cloudfoundry v2:
您需要先从V1服务迁移应用程序和数据
6月30日删除
cf是访问cloudfoundry v2的CLI,而vmc是访问cloudfoundry v1的CLI。我假设cloudfoundry v1(您在vmc登录中使用的用户)中的当前用户也必须迁移到v2(新的cf登录命令)。cloudfoundry v2位于端点api.run.pivotal.io之后
如果您在Cloud Foundry v1上注册了用户,则其凭据已复制到run.pivotal.io
快速启动:
gem install cf
cf target api.run.pivotal.io
cf login
完整文件:
迁移:您可以使用--sso成功登录。该命令看起来像
cf登录--sso
因此,它会要求您输入一些密码,您可以从web登录中检索这些密码 请注意,目前我确实登录了。然而,我无能为力: