Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getting 400 bad request #17

Closed
guy-mograbi-at-gigaspaces opened this issue Jun 12, 2014 · 4 comments
Closed

getting 400 bad request #17

guy-mograbi-at-gigaspaces opened this issue Jun 12, 2014 · 4 comments

Comments

@guy-mograbi-at-gigaspaces

I keep getting

ClientResponseException{message=Bad Request, status=400, status-code=BAD_REQUEST}

when I try to authenticate.

I simply copy pasted code from your homepage

  OSClient os = OSFactory.builder().endpoint("https://region-b.geo-1.identity.hpcloudsvc.com:35357/v2.0")
                .useNonStrictSSLClient(true)
                .credentials("***","***")
                .tenantName("***")
                .authenticate();

I am sure my details are correct because when I do an HTTP request myself, It succeeds.

gondor added a commit that referenced this issue Jun 12, 2014
…on properties and doesnt ignore them like openstack does
gondor added a commit that referenced this issue Jun 12, 2014
@gondor
Copy link
Member

gondor commented Jun 12, 2014

@guy-mograbi-at-gigaspaces thanks for reporting the issue. I actually didn't have an HP account so I created one to find the issue.

I have deployed the new 1.0.2 snapshots to Maven and updated the downloadable snapshot jars for 1.0.2 on the website.

One thing I did notice about HP is if your using a scoped tenant (at least in my case) it was expecting the tenantId vs tenantName. The Factory builder now offers a tenantName(tenantName) and tenantId(tenantId) when authenticating. You may need to use the tenantId.

Let me know if this works.

@guy-mograbi-at-gigaspaces
Copy link
Author

@gondor - thanks for the response, however I am unable to reference the 1.0.2 version.

using the snippet from your site

<dependency>
      <groupId>org.pacesys</groupId>
      <artifactId>openstack4j</artifactId>
      <version>1.0.2-SNAPSHOT</version>
</dependency>

and I get

[INFO] Failed to resolve artifact.

Missing:
----------
1) org.pacesys:openstack4j:jar:1.0.2-SNAPSHOT

@gondor
Copy link
Member

gondor commented Sep 1, 2014

Try running a mvn compile -U

The -U will force dependency updates. We publish to maven central so I'm not sure why your seeing this. You could also download source and then run a "mvn install" which will deploy the artifact locally for your dependent projects.

@gondor
Copy link
Member

gondor commented Sep 6, 2014

You can always clone openstack4j and then do a "mvn install" to build and deploy the artifact locally. Closing issue as workarounds have been provided. Re-open if needed.

@gondor gondor closed this as completed Sep 6, 2014
gondor added a commit that referenced this issue Jan 9, 2015
tongh-qtl added a commit to whaon/openstack4j that referenced this issue Nov 11, 2016
1.compute:ContainX#17 getImageId()
2.image:#1 out of range of int,should use Long
3.image:#2 “result” in GlanceTask should be a Map
4.image:#3 imageStatus in GlanceImage should be status
jsaroja66 pushed a commit to jsaroja66/openstack4j that referenced this issue Mar 13, 2020
Deprecate domain objects and builders for deprecated services
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants