On Tue, Jan 22, 2013 at 3:19 AM, li_fuqiong <li_fuqi...@venustech.com.cn> wrote:
> Dear All,
> I resolved this issue. My api port is 8096 but not 8080. Thank you.

Just so that you are aware, port 8096 is an un-authenticated API port.
 It allows you to perform any operation without authentication.  If
that is what you were looking for, then you should be fine.

However, port 8080 is the port that you would want to use when coming
in from an external source OR if you are providing API access to your
users.  If that's what you want to use, I'd suggest that you should
try to figure out how to get an API call to work correctly.  There are
many different CloudStack API language binding libraries, many of
which are easily used within shell scripts.

You might also want to take a look at the CloudStack CLI tool "CloudMonkey".

-chip


> 发送时间: 2013-01-22 15:47
> 收件人: cloudstack-dev@incubator.apache.org
> 主题: Creating the SSH Keypair error.
> Dear All,
>     My cloudstack version is 4.0.0.
> I want to create the SSH Keypair for integrating cloudstack with cloudify. I 
> followed instruction of "Apache CloudStack 4.0.0-incubating CloudStack 
> Installation Guide".
> Executed  the following command in cloudstack manager server.
> curl --globoff 
> http://localhost:8080/client/api?command=createSSHKeyPair&name=keypairdoc&account=admin&domainid=0f3e504c-ac34-4345-a705-17ecd298bd58
>
> The domainid is got from cloudstatck administrator portal and I can confirm 
> it's correct.
>
> But I got an error message of errorcode 401 and errortext is "unable to 
> verify user credentials and/or request signature".
>
> Then I alter the parameter of the command with apikey and signature as 
> follows:
> curl --globoff 
> http://localhost:8080/client/api?command=createSSHKeyPair&name=keypair-doc&domainid=0f3e504c-ac34-4345-a705-17ecd298bd58&apikey=JhBUZf7eF-hH58RFoivKDNPrGNTY_GGPvxEkhRcojW5ySBbb5RvSkwXw9utVWP6a3A-l1Ut9uIN6YbzKaNHb7Q&signature=S1CuL3TDI14kVjeLHfhmNgD_E-Ywc693cyTHKjxLdWKBUNugTrNeMzCEUDIgynB2q7d52nIBM_pQ4rdV6BziWw
>
> but I got the same error.
>
> Thank you all.

Reply via email to