IBM Aspera
Configuring the Veza integration for IBM Aspera on Cloud
Overview
The Veza integration for IBM Aspera on Cloud enables gathering User, Groups, Roles and Workspace memberships for the cloud-based file transfer platform.
Configuring Aspera
Generate a key pair to use for authentication (if creating a new user):
Use the command to generate the private portion
ssh-keygen -t rsa -b 4096 -m PEM -f jwtRS256.key
.Do not set a password.
Create a public key from the private key:
openssl rsa -in jwtRS256.key -pubout -outform PEM -out jwtRS256.key.pub
.
Create or use an existing user for authentication:
For a new user, set the user's public key to the public portion of the generated key pair.
For an existing user and key pair set, use the corresponding public key to configure the integration in Veza.
Go to Integrations -> API clients to create an API client:
Enter a name.
Enter the Veza URL for the Redirect URI.
Enable Enable JWT Grant type.
Deselect Client can retrieve token for all users and pick the configured user.
Click create and note the Client ID and Client Secret
Note the Aspera Organization name. This is your Aspera sub-domain, for example
https://<org_name>.ibmaspera.com
.
Configuring Aspera on the Veza Platform
On the Veza Integrations page, add a Aspera Integration with the following fields:
Name - Name for integration
Client Id - Client ID from the API client
Client Secret - Corresponding Client Secret
Username - Username for API client user with public key.
Organization Name - Aspera Organization name
Notes and Supported Entities
Aspera Users
Aspera Group
Aspera Workspace
Aspera Roles
Users are assigned roles to the Organization and Workspace based on their configured status
Organization Roles
Organization Admin
ATS Admin
Member
Workspace Roles
Manager
Member
Last updated