There are now two ways to authenticate your Cloud-A Bulk Storage account to CloudBerry products based on your workflows and requirements. The first method is Keystone authentication, which is the legacy method. Authenticating this way. 
The Cloud-A, CloudBerry Lab partnership has been great for our clients, providing a tried and tested use-case for backups of on-premise or Cloud-A hosted Windows servers (and soon to be Linux!)
You will notice a few changes in the Cloud-A/CloudBerry relationship. First of all, most CloudBerry OpenStack products now have a branded connector for Cloud-A. No longer will you have to choose the generic OpenStack account.
There are now two ways to authenticate your Cloud-A Bulk Storage account to CloudBerry products based on your workflows and requirements. The first method is Keystone authentication, which is the legacy method. Authenticating this way will allow for read and write access to all of the Bulk Storage containers in your Cloud-A Account.
With the release of Bulk Storage container keys, users can now authenticate to specific containers, rather than all of the containers in your account. Authenticating this way is ideal for service providers who manage backups for multiple customers. Instead of authenticating to the service provider’s Bulk Storage account where you would have access to all of the account’s containers, you authenticate to a specific client’s container.
Keystone Authentication for CloudBerry Labs Products (Legacy)
CloudBerry products can be used with OpenStack-based cloud storage services like Cloud-A (Bulk Storage.) Cloud-A supports Keystone authentication. OpenStack Keystone is a secure identity service that can be used for connecting CloudBerry products with OpenStack-based cloud storage service accounts.
Keystone Authentication is supported in the following CloudBerry Lab products:
When the CloudBerry application has launched you will notice that the left side of the screen represents your local systems folder directory and the right represents cloud storage. On the cloud storage side click the source drop down menu and select:
1. Select <New Storage Account>
2. Select Cloud-A as your cloud storage provider
3. Enter your specific credentials as follows:
- Display name: Email (Cloud-A login username)
- User name: Email (Cloud-A login username)
- Api key: Cloud-A password
- Authentication Service: https://keystone.ca-ns-1.clouda.ca:8443/v2.0/tokens
- Tenant Name: Email (Cloud-A login username)
4. Select “Test Connection” to ensure that the system has accepted your credentials.
If Test Connection fails, ensure that you have entered your credentials correctly. If you have entered your credentials correctly but are still receiving a “Connection Failed” error message, ensure that you have the correct ports open for Bulk Storage. Those ports are: 80, 443, 8443 and 8444.
If your credentials were entered correctly, the Bulk Storage container you created in the first step will appear in the file directory in the CloudBerry software.
Container Keys Authentication for CloudBerry Labs Products
Bulk Storage Container Keys allow Cloud-A Bulk Storage users to deploy more secure applications using access keys specific to the container(s) that each application, like CloudBerry, needs to use. You can generate secure keys on a per-container basis through the Dashboard with either read-only, or full read & write access — in case you need to give access to a third party to perform read operations on any object in a container.
Generating Read-Only or Full Access Keys
To generate read-only or full-access container keys, navigate to the storage dropdown menu in your Cloud-A dashboard and select containers. If you haven’t created a container yet, create and name one. The container will show up under your container list on the containers screen. Select “Manage Access”
You will see that neither full-access or read-only keys are assigned to your container by default. To created the keys, select “Generate Initial Keys.”
Both the full-access and read-only keys will be generated and displayed on the screen. These are the keys you can use to authenticate to OpenStack Swift compatible software like CloudBerry if you want to authenticate to a specific Bulk Storage container. At any time you can re-generate keys. The regeneration function serves to revoke your current container credentials, and generate new secure keys. This will help squelch the threat of any potentially leaked credentials by immediately rejecting all requests using the old keys, and certainly not having to worry about leaked account passwords per the OpenStack Swift default access requirements.
1. Select <New Storage Account>
2. Select Cloud-A as your cloud storage provider
3. Enter your specific credentials as follows:
- Display name: Container name
- User name: Read-key or Full-access (depending on your choice)
- Api key: Read-Only key or Full-Access key
- Authentication Service: https://ca-ns-1.bulkstorage.ca:8444/keys_auth/<container_name>/v2.0
- Tenant Name: Tenant ID
