Yes, I can confirm this! Order is not important.
I fixed my problem. Root cause was a wrong url encoding and that the api 
command is case sensitive.

@Emil thx for pushing me in the right direction! Helped a lot! :-)

-----Ursprüngliche Nachricht-----
Von: Wei ZHOU <[email protected]> 
Gesendet: Donnerstag, 26. Januar 2023 16:17
An: [email protected]
Betreff: Re: api signature not working

Hi,

The order is not important as far as I know.

-Wei



On Thu, 26 Jan 2023 at 14:49, <[email protected]> wrote:

> Thx Emil and Wei,
>
> I am using Zoho Deluge and it looks like hmac-sha1 hash is not correct 
> or at least is different.
>
> When creating the hash of the call all parameters including apikey and 
> command needed to be in alphabetic order, correct? But when I send the 
> api call with the signature the docu is not persistent. Do I need to 
> reorder the call I used to create the signature and start with command 
> and put apikey infront of signature?
>
> Regards,
> Swen
>
> -----Ursprüngliche Nachricht-----
> Von: Wei ZHOU <[email protected]>
> Gesendet: Donnerstag, 26. Januar 2023 14:44
> An: [email protected]
> Betreff: Re: api signature not working
>
> Hi,
>
> Do you use python ? As far as I remember, the same code works with 
> python2, but not with python3.
>
> -Wei
>
> On Thu, 26 Jan 2023 at 10:36, <[email protected]> wrote:
>
> > Hi,
> >
> >
> >
> > I want to use CS api to interact with some other services, but it 
> > looks like I do not get it to work.
> >
> > Is this still valid:
> >
> > http://docs.cloudstack.apache.org/en/latest/developersguide/dev.html
> > #m
> > aking-
> > api-requests
> > <http://docs.cloudstack.apache.org/en/latest/developersguide/dev.htm
> > l#
> > making-api-requests>
> >
> >
> >
> > I am using scripts which are working with other versions of CS, but 
> > it is not working in 4.17.2.0. I always get "unable to verify user 
> > credentials and/or request signature".
> >
> > Does someone using signed api calls with success in 4.17.2.0?
> >
> >
> >
> > Regards,
> >
> > Swen
> >
> >
>
>
>


Reply via email to