[
https://issues.apache.org/jira/browse/JCLOUDS-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761464#comment-13761464
]
Andrew Phillips commented on JCLOUDS-230:
-----------------------------------------
>From the eCloud API spec document (thanks for finding that, Darma!):
"The Live Specification is available through HTTP or HTTPS. For the Live
Specification, the Verizon Terremark URI is:
https://services.enterprisecloud.terremark.com
The href attribute for each call in this document begins with /cloudapi/ecloud
for access to an organization's live data. For example, the Action Layout
Groups Create call for Environment 1 in this document has a URI of:
https://services.enterprisecloud.terremark.com/cloudapi/ecloud/layoutGroups/environments/1/
... action/createLayoutGroup
However, for access to the Live Specification the href attribute begins with
/cloudapi/spec. Therefore, for the Live Specification the URI must be:
https://services.enterprisecloud.terremark.com/cloudapi/spec/layoutGroups/environments/1/
... action/createLayoutGroup
For CloudApi authentication:
* Full access is available to: access key: 33333333333333333333333333333333
private key: 3333333333333333333333333333333333333333333333333333333333333333.
* Readonly access is available to access key: 11111111111111111111111111111111
private key: 1111111111111111111111111111111111111111111111111111111111111111.
* No access is available to access key: 22222222222222222222222222222222
private key: 2222222222222222222222222222222222222222222222222222222222222222.
* Not found access is available to any other access key and private key.
For Basic authentication:
* Full access is available to any username, except as noted below, with the
password T3rr3m@rk.
* Readonly access is available to the username [email protected] and the
password T3rr3m@rk.
* No access is available to the username [email protected] and the
password T3rr3m@rk.
* Not found access is available to the username [email protected] and the
password T3rr3m@rk or to any username that does not have the password T3rr3m@rk.
The API requires authentication in every call included as part of the HTTP
header. To assist in creating the headers correctly, Verizon Terremark has
created an online tool that will take a few inputs regarding the call and
generate the appropriate headers.
The Signature Generator is available at:
https://services.enterprisecloud.terremark.com/cloudapi/spec/SignatureGenerator.aspx";
> Terremark eCloud support does not work
> --------------------------------------
>
> Key: JCLOUDS-230
> URL: https://issues.apache.org/jira/browse/JCLOUDS-230
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.6.1
> Reporter: Jaiganesh Mathaiyan
> Attachments: TerremarkECloudAPISampleRESTCalls.txt
>
>
> The login call is failing with below error.
> I am using the right Access key and Private Key (for API user) in the
> ContextBuilder. For provider string I am using "trmk-ecloud".
> Based on further discussion on the user forum the problem is because
> Terremark eCloud has deprecated the API version that jclouds initially based
> its development on.
> More details on the API support/deprecation can be found @
> http://support.theenterprisecloud.com/kb/default.asp?id=533&Lang=1&SID
> org.jclouds.rest.AuthorizationException: request: POST
> https://services.enterprisecloud.terremark.com/api/v0.8b-ext2.8/login
> HTTP/1.1 failed with response: HTTP/1.1 401 Unauthorized
> at
> org.jclouds.trmk.vcloud_0_8.handlers.ParseTerremarkVCloudErrorFromHttpResponse.handleError(ParseTerremarkVCloudErrorFromHttpResponse.java:73)
> ~[trmk-common-1.6.0.jar:1.6.0]
> at
> org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:69)
> ~[jclouds-core-1.6.0.jar:1.6.0]
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:182)
> ~[jclouds-core-1.6.0.jar:1.6.0]
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:152)
> ~[jclouds-core-1.6.0.jar:1.6.0]
> at
> org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.invoke(InvokeSyncToAsyncHttpMethod.java:133)
> ~[jclouds-core-1.6.0.jar:1.6.0]
> at
> org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.apply(InvokeSyncToAsyncHttpMethod.java:99)
> ~[jclouds-core-1.6.0.jar:1.6.0]
> at
> org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.apply(InvokeSyncToAsyncHttpMethod.java:60)
> ~[jclouds-core-1.6.0.jar:1.6.0]
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:159)
> ~[jclouds-core-1.6.0.jar:1.6.0]
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:126)
> ~[jclouds-core-1.6.0.jar:1.6.0]
> at $Proxy87.login(Unknown Source) ~[na:na]
> at
> org.jclouds.trmk.vcloud_0_8.config.TerremarkVCloudRestClientModule$22.get(TerremarkVCloudRestClientModule.java:488)
> ~[trmk-common-1.6.0.jar:1.6.0]
> at
> org.jclouds.trmk.vcloud_0_8.config.TerremarkVCloudRestClientModule$22.get(TerremarkVCloudRestClientModule.java:484)
> ~[trmk-common-1.6.0.jar:1.6.0]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
