I’m a bit embarrassed to say that my issue turned out to be related to the date & time on my client was not correct. So the “expires” parameter, sent by the cli, was a day behind the time on the mgmt server. I would have thought the integration api port would not work as well but that’s not the case because I assume security is not a big concern when using the integration api port. There was no need to modify anything other time on my client to get this working.
Thanks for all the help and sorry for the oversight. -- Antone @thehyperadvisor http://thehyperadvisor.com -- Antone Heyward Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Monday, May 19, 2014 at 6:21 PM, Phillip Kent wrote: > A problem we have experienced with cloudmonkey 5.1.0 in our CloudStack > platform (4.2.1) is that the GET request sent via HTTP contains the > argument > apikey=... > but our API server will only respond to > apiKey=... > > So if you edit the cloudmonkey source 'requester.py' at line 146, you > change > > args['apikey'] = ... > > to > > args['apiKey'] = ... > > I have not got to the bottom of why this changed in cloudmonkey, or > whether/why different versions of the CS API code work with apikey, > apiKey or both. Does anyone know?? > > You do also need to add lines to the cloudmonkey config file: > > [user] > username= > password= > > [server] > expires=600 > > (these relate to added functions for authentication, and blocking > malicious attacks) > > If you have a proxy server on the front of your actual server then you > could add a check so that apikey or apiKey will work. > > - Phillip > > > On Mon, 2014-05-19 at 16:08 +0200, Andrija Panic wrote: > > could you try: > > remove whole .cloudmonkey folder (settings/history,cache) > > just start cloudmonkey withOUT writing conf file. > > quit cloudmonkey (it will write it's config file) > > and then editing config file (I personaly have apikey, username, secretkey, > > password in that order) with usename/password being empty after the = > > sign... > > > > Also doublecheck api/secret keys... > > > > > > > > > > On 19 May 2014 16:01, Thehyperadvisor <thehyperadvi...@gmail.com > > (mailto:thehyperadvi...@gmail.com)> wrote: > > > > > Still does not work after rearranging the config. So now the config has > > > apikey = <key>, secretkey = <key>, username = (blank), password = (blank) > > > in that order. The error is the same. > > > > > > Sent from mobile device. > > > > > > > On May 19, 2014, at 9:18 AM, Thehyperadvisor <thehyperadvi...@gmail.com > > > > (mailto:thehyperadvi...@gmail.com)> > > > wrote: > > > > > > > > Just one other note. I actually tried as well with acs 4.2.1 and had the > > > same issue so figured it was a cloudmonkey issue. And of course the > > > integration api port worked fine with both acs 4.3 and 4.2.1. > > > > > > > > Sent from mobile device. > > > > > > > > > On May 19, 2014, at 8:50 AM, Thehyperadvisor > > > > > <thehyperadvi...@gmail.com (mailto:thehyperadvi...@gmail.com)> > > > wrote: > > > > > > > > > > Ok, I will try this. I did notice that when I did not have the > > > > > username > > > = or password = in the config I got the error saying that they were needed > > > but the order was as shown below. > > > > > > > > > > username = > > > > > apikey = > > > > > secretkey = > > > > > password = > > > > > > > > > > I will rearrange as you suggested when I get back to it. And yes, I > > > > > did > > > not have the issue in 5.0. > > > > > > > > > > Sent from mobile device. > > > > > > > > > > > On May 19, 2014, at 8:32 AM, sebgoa <run...@gmail.com > > > > > > (mailto:run...@gmail.com)> wrote: > > > > > > > > > > > > > > > > > > > On May 19, 2014, at 2:26 PM, Antone Heyward < > > > thehyperadvi...@gmail.com (mailto:thehyperadvi...@gmail.com)> wrote: > > > > > > > > > > > > > > 8080 > > > > > > > http > > > > > > > > > > > > > > > > > > > > > > > > > I am guessing that it used to work with cloud monkey 5.0 ? > > > > > > > > > > > > I have seen something strange but have not had time to look deeper > > > into it. > > > > > > > > > > > > Try this wacky thing: > > > > > > > > > > > > -edit your cloud monkey config file > > > > > > -remove the username/password entries (which are probably blank) > > > > > > -enter username = and password = lines after your api keys > > > > > > definition > > > > > > > > > > > > > > > > > > > > > , don't set any username and password. > > > > > > -save, exit > > > > > > -restart cloudmonkey. > > > > > > > > > > > > don't ask me why, it worked for me..and like I said, I had no time > > > > > > to > > > look into it. > > > > > > > > > > > > > > On May 19, 2014 3:41 AM, "Andrija Panic" > > > > > > > > <andrija.pa...@gmail.com (mailto:andrija.pa...@gmail.com)> > > > wrote: > > > > > > > > > > > > > > > > ports, http / https ? > > > > > > > > > > > > > > > > cheers > > > > > > > > > > > > > > > > > > > > > > > > > On 18 May 2014 23:58, Antone Heyward > > > > > > > > > <thehyperadvi...@gmail.com (mailto:thehyperadvi...@gmail.com)> > > > wrote: > > > > > > > > > > > > > > > > > > I am using a new install of acs 4.3 and cloudmonkey 5.1. > > > > > > > > > > > > > > > > > > I have setup the host, port, username, apikey, and secretkey > > > > > > > > > but > > > when I > > > > > > > > try > > > > > > > > > to sync i get: > > > > > > > > > > > > > > > > > > *Unauthorized:* None > > > > > > > > > > > > > > > > > > Failed to sync apis, please check your config? > > > > > > > > > > > > > > > > > > *Note:* `sync` requires api discovery service enabled on the > > > CloudStack > > > > > > > > > management server > > > > > > > > > > > > > > > > > > Has anyone else seen this? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Antone > > > > > > > > > @thehyperadvisor > > > > > > > > > http://thehyperadvisor.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > Andrija Panić > > > > > > > > -------------------------------------- > > > > > > > > http://admintweets.com > > > > > > > > -------------------------------------- > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
