Skip to main content

Manage

Your account is the starting point and your identity when accessing resources in the RemotiveCloud.

Connect to google​

RemotiveCloud currently only support Google accounts when using RemotiveCloud, but if you don't have one you can still use your existing business email as a Google account. How to accomplish this is explained here.

Personal access tokens​

To access RemotiveCloud resources using RemotiveCLI or code it can be cumbersome to always have a fresh access token. For those cases you can download and use a personal access token.

Personal access tokens are long lived tokens used to access RemotiveCloud resources as yourself. Unlike service account tokens, these access tokens are account wide and gives you access to anything your account has access to.

Its very important to handle access token files with care

Create personal access token​

Personal access tokens are stored as json files on your computer.

How-to create a personal access token

Step 1​

Navigate to your profile picture at the top right corner and press "Tokens" to see your existing tokens and create new tokens.

[Image] Personal access token step 1

Step 2​

Press "Create new token" to have a personal access token json file downloaded to your computer.

If you intend to use it from the CLI it's recommended to store it under ~/.config/.remotive directory so it can be picked up automatically by the CLI.

[Image] Add personal access token

Revoke​

Revoking an access token makes it unusable. A revoked access token can never be un-revoked. It's recommended to rotate your tokens at regular intervals by revoking and create new keys to minimize the risk for someone to get access to your token.

How-to revoke a personal access token

Step 1​

[Image] Revoke access token step 1

Step 2​

[Image] Revoke access token step 2

Use your access token​

Once your access token file is downloaded you need to make use of it either from the CLI or from code.

How-to use a personal access token

Make sure your file resides in ~/.config/.remotive directory​

If you downloaded you file with web console, make sure that you stored the file in this directory, otherwise copy the file there now. If you used the CLI to download your token file it's already stored under correct path.

Make sure that your token file is found​

$ remotive cloud auth tokens list-files personal-token-xxx.json

Check the content of the file​

$ remotive cloud auth tokens describe --file personal-token-xxx.json
{
    "expires": "2033-06-21",
    "token": "pa1.0/668DBF30-0DA51E61-13749692-BC760C7A-DAAAB37A-10721C63-6323B4E4-04E01C43",
    "created": "2023-06-21T13:01:19.447+02:00",
    "name": "xxx"
}

Activate the token to use this access token​

By using this command you are using your personal access token instead of the short-lived access token that you used with remotive auth login.

$ remotive cloud auth tokens activate personal-token-xxx.json
$ remotive cloud auth print-access-token
pa1.0/668DBF30-0DA51E61-13749692-BC760C7A-DAAAB37A-10721C63-6323B4E4-04E01C43

Its highly discouraged to copy/write your personal access token into scripts, code, or anything that can potentially leave your computer. If an access token is required use i.e environment variables to prevent this. This makes it possible for other users in your team to use the same code.

export ACCESS_TOKEN=$(remotive cloud auth print-access-token)

If your code has to run on non-personal machines it's recommended to use service-accounts there.

Profile​

To view your current profile, expand the account dropdown and select "Profile"

How-to access current profile

Step 1​

[Image] Profile in dropdown

Step 2​

[Image] Profile information overlay

Logout​

To log out of your current profile, expand the account dropdown and select "Logout"