The Auth API uses mTLS to authenticate a client-server connection. Therefore, the client must provide TLS certificates signed by the Auth server to access the API. These are easy to create and provide using Credential loaders.
The client certificates signed by the Auth server will be associated with a specific user. This user will be used to authorize API requests made by the client.
It is recommended to make a new user and role for each client. This makes it easier to track client actions, as well as carefully control client permissions.
For example, if your client needs to use
client.GetRole(), the user must have permission to perform the
action on the
role resource. You should create a user and role with the minimum permissions required.
When running Teleport in production, we recommend that you follow the practices below to avoid security incidents. These practices may differ from the examples used in this guide, which are intended for demo environments:
- Avoid using
sudoin production environments unless it's necessary.
- Create new, non-root, users and use test instances for experimenting with Teleport.
- Run Teleport's services as a non-root user unless required. Only the SSH
Service requires root access. Note that you will need root permissions (or
CAP_NET_BIND_SERVICEcapability) to make Teleport listen on a port numbered <
- Follow the "Principle of Least Privilege" (PoLP). Don't give users
permissive roles when giving them more restrictive roles will do instead.
For example, assign users the built-in
- When joining a Teleport agent to a cluster, save the invitation token to a
file. Otherwise, the token will be visible when examining the
teleportcommand that started the agent, e.g., via the
historycommand on a compromised system.
Copy and Paste the below and run on the Teleport Auth server.
cat > api-role.yaml <<EOF
- resources: ['role']
tctl create -f api-role.yaml
Add user and login via web proxy
tctl users add api-user --roles=api-role
See our roles documentation for more details on role based access control.
The Teleport Go client uses Credentials to gather and hold TLS certificates, connect to proxy servers over SSH, and perform some other actions.
Credentials are created by using Credential loaders, which gather certificates and data generated by Teleport CLIs.
Since there are several Credential loaders to choose from with distinct benefits, here's a quick breakdown:
- Profile Credentials are the easiest to get started with. All you have to do is log in to your device with
tsh login. Your Teleport proxy address and credentials will automatically be located and used.
- IdentityFile Credentials are the most well-rounded in terms of usability, functionality,
and customizability. Identity files can be generated through
tctl auth sign, making them ideal for both long-lived proxy and auth server connections.
- Key Pair Credentials have a much simpler implementation than the first two Credentials listed and may feel more familiar. These are good for authenticating clients hosted directly on the auth server.
- TLS Credentials leave everything up to the client user. This is mostly used internally, but some advanced users may find it useful.
Here are some more specific details to differentiate them by:
|Type||Profile Credentials||Identity Credentials||Key Pair Credentials||TLS Credentials|
|Ease of use||Easy||Easy||Medium||Hard|
|Supports long-lived certificates||Yes, but must be configured on server side||Yes||Yes||Yes|
|Supports SSH connections||Yes||Yes (6.1+)||No||No|
|Automatic Proxy Address discovery||Yes||No||No||No|
See the Credentials type on pkg.go.dev for more information and examples for Credentials and Credential Loaders.
The API client makes requests through an open connection to the Teleport Auth server.
If the Auth server is isolated behind a Proxy Server, a reverse tunnel connection can be made using SSH certificates signed by the auth server. You can either provide the server's reverse tunnel address directly or provide the web proxy address and have the client automatically retrieve the reverse tunnel address.
While all Credential loaders support mTLS connections, only some support SSH connections (see the chart above).
Take a look at this client constructor example to see what these connection options look like.