<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tokens on Layer5 Documentation</title><link>/tags/tokens/</link><description>Recent content in Tokens on Layer5 Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="/tags/tokens/index.xml" rel="self" type="application/rss+xml"/><item><title>Create and Use an API Token</title><link>/cloud/guides/security/api-tokens/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/cloud/guides/security/api-tokens/</guid><description>&lt;p&gt;An API token lets a script, a CI job, or a Meshery client act as your user account against Layer5 Cloud. This guide creates one, uses it, rotates it, and revokes it. For what a token can reach and why it never expires, read the &lt;a href="/cloud/concepts/identity-and-security/tokens/"&gt;Tokens concept&lt;/a&gt;.&lt;/p&gt;

&lt;h2 id="before-you-start" class="heading-link"&gt;
 Before you start
 &lt;a href="#before-you-start" class="heading-anchor" aria-label="Permalink to this heading"&gt;🔗&lt;/a&gt;
&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;You need the &lt;strong&gt;Create Token&lt;/strong&gt; permission to create a token in the interface. Organization Admin and Provider Admin hold it by default. A user without it sees the create control disabled.&lt;/li&gt;
&lt;li&gt;You need &lt;strong&gt;View Tokens&lt;/strong&gt; to open the Tokens tab. Every default user role holds it.&lt;/li&gt;
&lt;li&gt;Decide which consumer gets this token. Create one token per consumer so you can revoke one without breaking the others.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id="create-a-token" class="heading-link"&gt;
 Create a token
 &lt;a href="#create-a-token" class="heading-anchor" aria-label="Permalink to this heading"&gt;🔗&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Open the Tokens tab under Security and start a new token. Enter a name and a purpose. Both are labels that appear in the token list: name the consumer (&amp;ldquo;ci-snapshots&amp;rdquo;), and state what it does in the purpose.&lt;/p&gt;</description></item><item><title>Security Reference</title><link>/cloud/reference/security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/cloud/reference/security/</guid><description>&lt;p&gt;This page states how keys, keychains, tokens, and sessions behave, exactly, as of Layer5 Cloud v1.0.278. For the model, read the &lt;a href="/cloud/concepts/identity-and-security/keys/"&gt;Keys&lt;/a&gt;, &lt;a href="/cloud/concepts/identity-and-security/keychains/"&gt;Keychains&lt;/a&gt;, &lt;a href="/cloud/concepts/identity-and-security/sessions/"&gt;Sessions&lt;/a&gt;, and &lt;a href="/cloud/concepts/identity-and-security/tokens/"&gt;Tokens&lt;/a&gt; concepts. For tasks, use the &lt;a href="/cloud/guides/security/"&gt;security guides&lt;/a&gt;. For base URL, authentication, and the organization header, see the &lt;a href="/cloud/reference/api-reference/"&gt;Cloud API&lt;/a&gt;. All paths below sit under &lt;code&gt;/api&lt;/code&gt; unless noted.&lt;/p&gt;

&lt;h2 id="permission-keys" class="heading-link"&gt;
 Permission keys
 &lt;a href="#permission-keys" class="heading-anchor" aria-label="Permalink to this heading"&gt;🔗&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Provider Admin holds every key. The table lists the default holders of the other roles. &amp;ldquo;Interface&amp;rdquo; means the control or tab is disabled or replaced by a permission error screen. &amp;ldquo;Server&amp;rdquo; means the Layer5 Cloud server refuses the request with HTTP 403.&lt;/p&gt;</description></item><item><title>Security</title><link>/cloud/guides/security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/cloud/guides/security/</guid><description>&lt;p&gt;These guides cover the security tasks in Layer5 Cloud. For how keys, keychains, and roles combine into permissions, read the &lt;a href="/cloud/concepts/identity-and-security/keys/"&gt;Keys&lt;/a&gt; and &lt;a href="/cloud/concepts/identity-and-security/keychains/"&gt;Keychains&lt;/a&gt; concepts. For defaults, lifetimes, and endpoints in one place, see the &lt;a href="/cloud/reference/security/"&gt;Security Reference&lt;/a&gt;.&lt;/p&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;I want to&lt;/th&gt;
 &lt;th&gt;Go to&lt;/th&gt;
 &lt;th&gt;Permission needed&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;Authenticate a script or CI job to Layer5 Cloud&lt;/td&gt;
 &lt;td&gt;&lt;a href="/cloud/guides/security/api-tokens/"&gt;Create and Use an API Token&lt;/a&gt;&lt;/td&gt;
 &lt;td&gt;Create Token, Download Token&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Stop a leaked or retired token from working&lt;/td&gt;
 &lt;td&gt;&lt;a href="/cloud/guides/security/api-tokens/#revoke-a-token"&gt;Revoke an API Token&lt;/a&gt;&lt;/td&gt;
 &lt;td&gt;Delete Token&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Rotate a token without breaking a pipeline&lt;/td&gt;
 &lt;td&gt;&lt;a href="/cloud/guides/security/api-tokens/#rotate-a-token"&gt;Rotate a token&lt;/a&gt;&lt;/td&gt;
 &lt;td&gt;Create Token, Delete Token&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;See where I am signed in and end a session&lt;/td&gt;
 &lt;td&gt;&lt;a href="/cloud/guides/security/sessions/"&gt;Review and Sign Out Sessions&lt;/a&gt;&lt;/td&gt;
 &lt;td&gt;View Sessions, Delete Token&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Group keys into a custom keychain&lt;/td&gt;
 &lt;td&gt;&lt;a href="/cloud/guides/security/custom-keychains/"&gt;Build a Custom Keychain&lt;/a&gt;&lt;/td&gt;
 &lt;td&gt;Create Keychain, Edit Keychain, Delete Keychain&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;</description></item></channel></rss>