cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rohit Yadav <bhais...@apache.org>
Subject Re: getting "Unauthorized: None" with cloudmonkey
Date Tue, 20 May 2014 02:57:18 GMT
Hi Philip,

Thanks for sharing the issue. In the config file (your
~/.cloudmonkey/config) all keys are lowercase. In requestor.py you're
correct that the key should be 'apiKey', in a recent merge conflict it was
incorrectly resolved in the commit 61901f20 on master branch. We'll issue a
new fix as soon as possible.

Regards,
Rohit Yadav


On Tue, May 20, 2014 at 3:51 AM, Phillip Kent <phillip.kent@gmail.com>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 <thehyperadvisor@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 <
> thehyperadvisor@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 <
> thehyperadvisor@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 <runseb@gmail.com> wrote:
> > > >>>
> > > >>>
> > > >>>> On May 19, 2014, at 2:26 PM, Antone Heyward <
> > > thehyperadvisor@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.panic@gmail.com>
> > > wrote:
> > > >>>>>
> > > >>>>> ports, http / https ?
> > > >>>>>
> > > >>>>> cheers
> > > >>>>>
> > > >>>>>
> > > >>>>>> On 18 May 2014 23:58, Antone Heyward <thehyperadvisor@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
> > > >>>>> --------------------------------------
> > > >>>
> > >
> >
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message