cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reshad Bashir (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9191) ACS 4.6 Custom Offer Signature mismatch "ERROR : "unable to verify user credentials and/or request signature""
Date Tue, 05 Dec 2017 10:37:00 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278368#comment-16278368
] 

Reshad Bashir commented on CLOUDSTACK-9191:
-------------------------------------------

We too are experiencing this issue and it is very frustrating as it makes building a good
application for Cloudstack very difficult. 

> ACS 4.6 Custom Offer Signature mismatch "ERROR : "unable to verify user credentials and/or
request signature""
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9191
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9191
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.6.0
>         Environment: ACS 4.6 with KVM hypervisors
>            Reporter: AssistanZ Networks Pvt
>            Priority: Minor
>              Labels: newbie
>
> ERROR : "unable to verify user credentials and/or request signature"
> Request to CloudStack without custom offering through application :
> apiKey=lGMCRQI6maiFCDsKuZAHI63u1upxCrUnNrWbXAnUZZE_qyEv7ozK_yNzYvNfXgX5x5mRcedIKynzSyLA5hf8yg&command=deployVirtualMachine&displayname=admin&displayvm=true&domainid=3776269a-949d-11e5-b907-e06995a35804&keyboard=us&name=priya&networkids=7efa5852-7e1f-4a26-9351-00f9d863aa3e&projectid=527ebed8-23f6-4c9f-9ee0-05926b035b1e&response=json&serviceofferingid=cb9fe060-1870-4bd0-8c0e-3980107acce6&templateid=96e753af-5e1a-4bf9-a28a-9f609ee06202&zoneid=af3ed220-7e36-4459-a6ea-9587a18246c0&signature=FU4xL%2FdGsYoihfWdvT%2FPrwwzthQ%3D
> This is working fine.
> Request to CloudStack with custom offering through application :
> apiKey=lGMCRQI6maiFCDsKuZAHI63u1upxCrUnNrWbXAnUZZE_qyEv7ozK_yNzYvNfXgX5x5mRcedIKynzSyLA5hf8yg&command=deployVirtualMachine&details%5B0%5D.cpuNumber=3&details%5B0%5D.cpuSpeed=1500&details%5B0%5D.memory=512&hypervisor=KVM&iptonetworklist%5B0%5D.networkid=7efa5852-7e1f-4a26-9351-00f9d863aa3e&response=json&serviceofferingid=a1613485-8cdf-4d84-8b97-8c2695128a2f&templateid=37acb430-949d-11e5-b907-e06995a35804&zoneid=af3ed220-7e36-4459-a6ea-9587a18246c0&signature=FU4xL%2FdGsYoihfWdvT%2FPrwwzthQ%3D
> ERROR : "unable to verify user credentials and/or request signature"
> Values are mapped same as CloudStack command string formation.
> It is generating same signature for both. Noticed difference in CloudStack is cpuSpeed
and cpuNumber. In both Speed and Number, first letter in upper case. During signature generation
we will convert all the values to lower case.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message