Skip to main content

Credentials for a project

The project's Access page holds everything used to reach the project outside the portal. Each kind of credential belongs to one project on one cloud, and none of them grants more than you already hold there.

CredentialForBound to
Application credentialThe OpenStack APIs — CLI, SDKs, TerraformYou, in this project
API userTools that need a username and passwordA second Keystone user in this project
S3/EC2 credentialS3-compatible object storage clientsYou, in this project
SSH keySigning in to servers you createThe key pair, used at server creation

Application credentials​

The recommended way to reach the OpenStack APIs. Issued to you, revocable on its own, and carrying no password. Covered step by step in Access the cloud APIs.

API users​

Some tools cannot use an application credential and expect a username and password. An API user is a second Keystone user inside the project for exactly that case — one for a backup agent, a monitoring probe or a legacy client.

Open Access → API Users and select Create User. OSIE creates the Keystone user in the project, grants it the project's roles, and shows the username and password once. Generate password issues a new password later and can download a matching openrc file:

backup-agent.openrc
#!/usr/bin/env bash
export OS_AUTH_TYPE=password
export OS_AUTH_URL=https://keystone.example.com/v3
export OS_IDENTITY_API_VERSION=3
export OS_REGION_NAME=eu-central-1
export OS_INTERFACE=public
export OS_PROJECT_DOMAIN_NAME=acme
export OS_USER_DOMAIN_NAME=acme
export OS_PROJECT_ID=<project-id>
export OS_USERNAME=<username>
export OS_PASSWORD=<password>

An API user exists independently of the person who created it, so it keeps working when that person leaves the project. Delete it when the tool using it is retired.

caution

An API user has the project's full role set. Prefer an application credential where the tool supports one — it is bound to you, and deleting it never affects anyone else.

S3/EC2 credentials​

An access key and a secret key for object storage clients that speak the S3 protocol. Open Access → S3/EC2 Credentials and select Create S3/EC2 Credential; the pair is displayed on creation.

They are available on clouds whose object storage exposes an S3-compatible endpoint.

SSH keys​

Key pairs used when creating servers, so you can sign in to them afterwards. Open Access → SSH Keys to add an existing public key or create a pair. An SSH key gets you into a server; it plays no part in authenticating to the cloud APIs. Deleting one leaves servers already created with it untouched.

Replacing and removing​

Every credential can be deleted from its list, and takes effect immediately. Secrets are shown once at creation and never again: to replace one, create the new credential, move the tool over to it, then delete the old one.

Leaving a project ends all of them — your roles on the project are withdrawn, and no credential issued for it can authenticate any longer.