<?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: Backup/Restore radius secret in Network Platform API</title>
    <link>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429753#M4877</link>
    <description>&lt;P&gt;It's a funny one with secrets in the API. On the one hand I understand why they don't allow downloading them but on the other hand if you have permissions to upload a new one and replace it with your own, then why wouldn't you have permissions to download the existing one.&lt;/P&gt;&lt;P&gt;As it currently stands we store various secret separately and when we hit endpoints that require uploading secrets then we apply them from our secret store at that point. &lt;/P&gt;</description>
    <pubDate>Tue, 14 May 2024 07:41:46 GMT</pubDate>
    <dc:creator>daniel_abbatt</dc:creator>
    <dc:date>2024-05-14T07:41:46Z</dc:date>
    <item>
      <title>Backup/Restore radius secret</title>
      <link>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429752#M4876</link>
      <description>&lt;P&gt;Hi, using API it is not possible to retrieve the secret but it is possible to set one. The same for MQTT Broker settings.&lt;/P&gt;&lt;P&gt;I understand is is for security reason but it is really important to be able to backup and restore passwords using API.&lt;/P&gt;&lt;P&gt;A solution could be to retrieve encrypted (salted, hashed) password with a prefix, like sha256:xxxxxxxxxxxxx and when restoring the endpoint should use the already hashed password if a matching prefix exists or set as plaintext password if not.&lt;/P&gt;&lt;P&gt;This way it would be possible to restore previously saved configurations and security will be always enforced.&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2024 06:58:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429752#M4876</guid>
      <dc:creator>francesco.boscarino</dc:creator>
      <dc:date>2024-05-14T06:58:37Z</dc:date>
    </item>
    <item>
      <title>Re: Backup/Restore radius secret</title>
      <link>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429753#M4877</link>
      <description>&lt;P&gt;It's a funny one with secrets in the API. On the one hand I understand why they don't allow downloading them but on the other hand if you have permissions to upload a new one and replace it with your own, then why wouldn't you have permissions to download the existing one.&lt;/P&gt;&lt;P&gt;As it currently stands we store various secret separately and when we hit endpoints that require uploading secrets then we apply them from our secret store at that point. &lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2024 07:41:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429753#M4877</guid>
      <dc:creator>daniel_abbatt</dc:creator>
      <dc:date>2024-05-14T07:41:46Z</dc:date>
    </item>
    <item>
      <title>Re: Backup/Restore radius secret</title>
      <link>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429754#M4878</link>
      <description>&lt;P&gt;If this is important, I would use a "secrets" manager.&lt;/P&gt;&lt;P&gt;I've used Amazon AWS Cognito before.  You can do things like have the script authenticate the user (to verify they are allowed to retrieve the secret), and then get it.  I have used Cognito for storing Meraki API keys as well.  And if you want to get tricky, you can also team it up with a lamba script to automatically and regularly rotate the API key.  When the API key is no longer stored anywhere except the secrets manager, regularly changing it becomes easy.&lt;/P&gt;&lt;P&gt;&lt;A href="https://aws.amazon.com/pm/cognito/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://aws.amazon.com/pm/cognito/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I am quite a fan of the Bitwarden password manager because of its enterprise features.  They also do a secrets manager - and they have a *free* plan option as well.&lt;/P&gt;&lt;P&gt;&lt;A href="https://bitwarden.com/products/secrets-manager/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://bitwarden.com/products/secrets-manager/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2024 21:04:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429754#M4878</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2024-05-14T21:04:34Z</dc:date>
    </item>
    <item>
      <title>Re: Backup/Restore radius secret</title>
      <link>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429755#M4879</link>
      <description>&lt;P&gt;Hi, this is not something related to where store secrets. The issue is that it is not possible to create a backup script which it's able to retrieve all the required information, secrets included. This is to have a working configuration backup which could be restore if required. If the radius secret is missing, it is not possible to restore the radius configuration.&lt;/P&gt;&lt;P&gt;If we can retrieve the secret, also in encrypted form for security, we could later restore the configuration, including the secret (already encrypted).&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2024 08:33:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429755#M4879</guid>
      <dc:creator>francesco.boscarino</dc:creator>
      <dc:date>2024-05-16T08:33:51Z</dc:date>
    </item>
    <item>
      <title>Re: Backup/Restore radius secret</title>
      <link>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429756#M4880</link>
      <description>&lt;P&gt;I did not explain my answer well.&lt;/P&gt;&lt;P&gt;Correct - you can not retrieve a RADIUS secret.  What you could do is store the RADIUS secret in a secrets manager.  When you provision or restore a network, always provision the RADIUS secret from the secrets manager.&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2024 08:51:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429756#M4880</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2024-05-16T08:51:49Z</dc:date>
    </item>
    <item>
      <title>Re: Backup/Restore radius secret</title>
      <link>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429757#M4881</link>
      <description>&lt;P&gt;You are right but if writing a tool, not only for my configurations, the tool does not have history of the secret, it should retrieve from API and restore if necessary.&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2024 08:54:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/backup-restore-radius-secret/m-p/5429757#M4881</guid>
      <dc:creator>francesco.boscarino</dc:creator>
      <dc:date>2024-05-16T08:54:07Z</dc:date>
    </item>
  </channel>
</rss>

