This page describes how switch enterprises via API. To switch enterprises means that an administrator can change from one tenant to another in order to work with another tenant. This is useful because you can only access some Abiquo entities and resources from within the enterprise that they belong to. For example, you must switch to an enterprise to deploy in its virtual datacenters or to edit its VM templates in the Apps library.
You will need the following resources:
- More than one enterprise created in the platform
Your user role must include the following privileges.
- ENTERPRISE_ENUMERATE
- ENTERPRISE_ADMINISTER_ALL
Your user must have the new enterprise within your management scope.
The following pages describe the switch enterprise functionality in the Abiquo UI.
Summary diagram
The steps in this diagram link to the API reference guide resources and data entities sections.
Detailed steps
Get the user entity by name
To get an administrator from the enterprise they are currently working in, without knowing the enterprise ID, use a URL with a wildcard for all enterprises, which is the underscore character "_".
If you know the ID of the user, you can retrieve the user entity directly with the users link.
For example, the cloud admin user has an ID of 1, so the link would be: "https://example.com/api/admin/enterprises/_/users/1"Or use the "has" parameter to perform a search for the user by text such as username, name, or details
curl -X GET \ 'https://example.com/api/admin/enterprises/_/users?has=cloudadmin' \ -H 'Accept: application/vnd.abiquo.users+json;version=4.7' \ -u admin:xabiquo k --verbose | jq .
This request returns a collection of users. Keep the required user entity, which starts with the braces before its ID
Get the new enterprise by name
curl -X GET \ 'https://example.com/api/admin/enterprises?has=Finance' \ -H 'Accept: application/vnd.abiquo.enterprises+json;version=4.7' \
Sample response
Find the required enterprise in the collection
Save the enterprise "edit" link
{ "title": "Finance Department", "rel": "edit", "type": "application/vnd.abiquo.enterprise+json", "href": "https://example.com:443/api/admin/enterprises/2" },
Edit the user entity to add the new enterprise link
Find the link with the "rel" value of "enterprise" and replace it with the new enterprise link. For example, to switch to enterprise 2, you could use the link below
Remember that the user entity must be complete in order to save the user, e.g. add an email attribute for the user because it is required.
Sample enterprise link
{ "href": "https://example.com/api/admin/enterprises/2", "rel": "enterprise" }
Sample user entity with new enterprise link
Update the user in any enterprise
In the user URL, replace the enterprise ID with a wildcard to represent all enterprises, which is the underscore character "_".
Perform a PUT request to the user, sending the updated user entity
cURL request
curl -X PUT \ https://example.com/api/admin/enterprises/_/users/10 \ -H 'Accept: application/vnd.abiquo.user+json;version=4.7' \ -H 'Content-Type: application/vnd.abiquo.user+json;version=4.7' \ -u user:password --verbose \ -d @requestpayload.json
Sample response. Success status code: 200