> +api.getVirtualGuestApi();
> +api.getDatacenterApi();
> +api.getSoftwareDescriptionApi();
> +api.getVirtualGuestBlockDeviceTemplateGroupApi();
> +api.getAccountApi();
> +
> +// Be sure to close the context when done
> +computeServiceContext.close();
> +{% endhighlight %}
> +
> +## SoftLayer Object Storage
> +SoftLayer Object Storage is an OpenStack® based blobstore storage system.
> +
> +{% highlight java %}
> +// Get a context with softlayer that offers the portable BlobStore API
> +BlobStoreContext context = ContextBuilder.newBuilder("swift")>From looking at [Auth >Endpoints](http://sldn.softlayer.com/article/Introduction-Object-Storage#Authentication_Endpoints) > it seems clear it's TempAuth only. These instructions really shouldn't be written based on deprecated code. We really don't need another thing blocking us from removing `"swift"`. The proper thing to do here is to update the instructions to use the [SwiftAuthenticationModule](http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/openstack/swift/v1/config/SwiftAuthenticationModule.html) When KeystoneProperties.CREDENTIAL_TYPE is set to tempAuthCredentials, do not use Keystone. Instead, bridge TempAuth to Keystone by faking a service catalog out of the storage url. The endpoint must be set to the TempAuth url, usually ending in auth/v1.0/. Unfortunately that will only be in the next release. I propose we remove Object Storage from this particular PR and update this guide with the SwiftAuthenticationModule when the next version of jclouds is released. The alternative is to leave it as is (basically recommending users to use deprecated code) and update this guide with the SwiftAuthenticationModule when the next version of jclouds is released. Your call @andreaturli --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/134/files#r23169800
