<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cluster management API Token in Dynatrace API</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-API/Cluster-management-API-Token/m-p/126460#M1108</link>
    <description>&lt;P&gt;Hi Sebastian, &lt;/P&gt;&lt;P&gt;thanks for sharing your feedback. Indeed if a token gets leaked, you are doomed - that's why you should keep your tokens safe e.g. never store it as a plaintext in your configuration repository or scripts. &lt;/P&gt;&lt;P&gt;As the warning suggests - you should keep the scope of the token as low as possible to minimize the impact of token leakage.  &lt;/P&gt;&lt;P&gt;Moreover, I encourage to implement a token rotation by using Cluster API (/tokens).&lt;/P&gt;&lt;P&gt;As you are all cluster administrators - you all should share same principles of security. &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;What else I can help you with?&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 07 Jan 2020 14:56:38 GMT</pubDate>
    <dc:creator>Radoslaw_Szulgo</dc:creator>
    <dc:date>2020-01-07T14:56:38Z</dc:date>
    <item>
      <title>Cluster management API Token</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Cluster-management-API-Token/m-p/126459#M1107</link>
      <description>&lt;P&gt;just input for dynatrace.&lt;/P&gt;&lt;P&gt;during the creation of a new API token for cluster management, there are 2 access you can grant into the new token&lt;/P&gt;&lt;P&gt;1) Cluster token management&lt;/P&gt;&lt;P&gt;2) Service Provider API&lt;/P&gt;&lt;P&gt;if I choose both, it asks not to put all access into 1 token, for security reasons ok fine split into 2 tokens. Then Save.&lt;/P&gt;&lt;P&gt;Until I realize that another admin has the same token that I just generated.&lt;/P&gt;&lt;P&gt;what kind of security is this?&lt;/P&gt;&lt;P&gt;if 1 of the admin got hacked, we are doomed&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Dynatrace Cluster version 1.178.128,20191030-143701&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Jan 2020 02:38:16 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Cluster-management-API-Token/m-p/126459#M1107</guid>
      <dc:creator>handjojo_sebast</dc:creator>
      <dc:date>2020-01-07T02:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster management API Token</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Cluster-management-API-Token/m-p/126460#M1108</link>
      <description>&lt;P&gt;Hi Sebastian, &lt;/P&gt;&lt;P&gt;thanks for sharing your feedback. Indeed if a token gets leaked, you are doomed - that's why you should keep your tokens safe e.g. never store it as a plaintext in your configuration repository or scripts. &lt;/P&gt;&lt;P&gt;As the warning suggests - you should keep the scope of the token as low as possible to minimize the impact of token leakage.  &lt;/P&gt;&lt;P&gt;Moreover, I encourage to implement a token rotation by using Cluster API (/tokens).&lt;/P&gt;&lt;P&gt;As you are all cluster administrators - you all should share same principles of security. &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;What else I can help you with?&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Jan 2020 14:56:38 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Cluster-management-API-Token/m-p/126460#M1108</guid>
      <dc:creator>Radoslaw_Szulgo</dc:creator>
      <dc:date>2020-01-07T14:56:38Z</dc:date>
    </item>
  </channel>
</rss>

