<?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: Read Only User in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Read-Only-User/m-p/16902#M3979</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Chris,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no easy way to create a role with privilage to access all read-only APIs. If you create a privilage with api-* then it provides access to all the APIs. You have to explicitly list out read only APIs like api-system-*, api-qtree-list-* .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rashmi.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Mar 2009 10:16:23 GMT</pubDate>
    <dc:creator>rashmid</dc:creator>
    <dc:date>2009-03-04T10:16:23Z</dc:date>
    <item>
      <title>Read Only User</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Read-Only-User/m-p/16897#M3978</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'd like to be able to secure an API user that would have read-only access to the filer. Going through RBAC, this seems possible, but there are too many options to successfully create a role based on this. The command errors as it's too long, and if I load it into a text file and run it using source, it reports the command is too long. I won't post the full list of "api-" RBAC roles I want to give the user as it's a bit big!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there an easy way of creating a read-only api-* user?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:30:14 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Read-Only-User/m-p/16897#M3978</guid>
      <dc:creator>chriskranz</dc:creator>
      <dc:date>2025-06-05T07:30:14Z</dc:date>
    </item>
    <item>
      <title>Re: Read Only User</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Read-Only-User/m-p/16902#M3979</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Chris,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no easy way to create a role with privilage to access all read-only APIs. If you create a privilage with api-* then it provides access to all the APIs. You have to explicitly list out read only APIs like api-system-*, api-qtree-list-* .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rashmi.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Mar 2009 10:16:23 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Read-Only-User/m-p/16902#M3979</guid>
      <dc:creator>rashmid</dc:creator>
      <dc:date>2009-03-04T10:16:23Z</dc:date>
    </item>
    <item>
      <title>Re: Read Only User</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Read-Only-User/m-p/16905#M3980</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply. However that's the problem I have. I've been through all the api- roles and highlighted the read-only ones, But the command line input buffer isn't long enough to accept this into a single role. If there was a way that I could add additional settings to an existing role, then I could build this up, but there doesn't seem to be, it just overwrites the existing settings.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Mar 2009 10:20:16 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Read-Only-User/m-p/16905#M3980</guid>
      <dc:creator>chriskranz</dc:creator>
      <dc:date>2009-03-04T10:20:16Z</dc:date>
    </item>
    <item>
      <title>Re: Read Only User</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Read-Only-User/m-p/16910#M3981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can use useradmin category APIs to overcome the limitations of CLI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rashmi.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Mar 2009 10:24:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Read-Only-User/m-p/16910#M3981</guid>
      <dc:creator>rashmid</dc:creator>
      <dc:date>2009-03-04T10:24:01Z</dc:date>
    </item>
    <item>
      <title>Re: Read Only User</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Read-Only-User/m-p/16915#M3982</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe you can break the api-* list to multiple roles, each one having different apis as capabilities.  Then add these roles to a group, then assign a read only user to this group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, create the roles you need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Name:    testrole&lt;/P&gt;&lt;P&gt;Info:&lt;/P&gt;&lt;P&gt;Allowed Capabilities: api-*&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Name:    login&lt;/P&gt;&lt;P&gt;Info:&lt;/P&gt;&lt;P&gt;Allowed Capabilities: cli-*,login-ssh,login-telnet&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create a group for these roles:&lt;/P&gt;&lt;P&gt;Name: testgrp&lt;/P&gt;&lt;P&gt;Info:&lt;/P&gt;&lt;P&gt;Rid: 131085&lt;/P&gt;&lt;P&gt;Roles: testrole,login&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assign user to this role.&lt;/P&gt;&lt;P&gt;Name: testuser&lt;/P&gt;&lt;P&gt;Info:&lt;/P&gt;&lt;P&gt;Rid: 131092&lt;/P&gt;&lt;P&gt;Groups: testgrp&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if this works!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Mar 2009 10:29:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Read-Only-User/m-p/16915#M3982</guid>
      <dc:creator>nagendrk</dc:creator>
      <dc:date>2009-03-04T10:29:31Z</dc:date>
    </item>
  </channel>
</rss>

