<?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: How API Client authenticating TRex in Tools</title>
    <link>https://community.cisco.com/t5/tools/how-api-client-authenticating-trex/m-p/3483841#M140</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hanoh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, we just begun TReX Evaluation and started with some LAB use cases&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One of the use cases is to expose TRex REST API to various team and they will execute (self-service) predefined profiles as part of onboarding process and get the Load test results.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-         We want to limit the REST API access with authentication (Credentials/Session Token)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-         User allowed to execute tests only for the profiles that assigned to them (Role Based Access Control)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have workaround/solution would be good, otherwise we will achieve this through API Proxy as interim workaround&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank You,&lt;/P&gt;&lt;P&gt;Rias&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Jan 2018 09:33:16 GMT</pubDate>
    <dc:creator>riasudeen</dc:creator>
    <dc:date>2018-01-24T09:33:16Z</dc:date>
    <item>
      <title>How API Client authenticating TRex</title>
      <link>https://community.cisco.com/t5/tools/how-api-client-authenticating-trex/m-p/3483839#M138</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We require CTReXClient Module authentication to TRex REST daemon &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help me understand what authentication mechanism currently available?&lt;/P&gt;&lt;P&gt;Also would like to know anything Roadmap related to RBAC (Access Control) for API Clients &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank You,&lt;/P&gt;&lt;P&gt;Rias&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Jan 2018 14:55:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/tools/how-api-client-authenticating-trex/m-p/3483839#M138</guid>
      <dc:creator>riasudeen</dc:creator>
      <dc:date>2018-01-23T14:55:51Z</dc:date>
    </item>
    <item>
      <title>Re: How API Client authenticating TRex</title>
      <link>https://community.cisco.com/t5/tools/how-api-client-authenticating-trex/m-p/3483840#M139</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rias,&lt;/P&gt;&lt;P&gt;Interesting question.&lt;/P&gt;&lt;P&gt;Can you elaborate why do you need that?&lt;/P&gt;&lt;P&gt;Are you using TRex?&lt;/P&gt;&lt;P&gt;It is not on our roadmap.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hanoh&lt;/P&gt;&lt;P&gt;Sent from my iPhone&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Jan 2018 22:16:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/tools/how-api-client-authenticating-trex/m-p/3483840#M139</guid>
      <dc:creator>hhaim@cisco.com</dc:creator>
      <dc:date>2018-01-23T22:16:33Z</dc:date>
    </item>
    <item>
      <title>Re: How API Client authenticating TRex</title>
      <link>https://community.cisco.com/t5/tools/how-api-client-authenticating-trex/m-p/3483841#M140</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hanoh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, we just begun TReX Evaluation and started with some LAB use cases&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One of the use cases is to expose TRex REST API to various team and they will execute (self-service) predefined profiles as part of onboarding process and get the Load test results.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-         We want to limit the REST API access with authentication (Credentials/Session Token)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-         User allowed to execute tests only for the profiles that assigned to them (Role Based Access Control)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have workaround/solution would be good, otherwise we will achieve this through API Proxy as interim workaround&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank You,&lt;/P&gt;&lt;P&gt;Rias&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jan 2018 09:33:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/tools/how-api-client-authenticating-trex/m-p/3483841#M140</guid>
      <dc:creator>riasudeen</dc:creator>
      <dc:date>2018-01-24T09:33:16Z</dc:date>
    </item>
    <item>
      <title>Re: How API Client authenticating TRex</title>
      <link>https://community.cisco.com/t5/tools/how-api-client-authenticating-trex/m-p/3483842#M141</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Understood,The proxy would work and it is not so complex.&lt;/P&gt;&lt;P&gt;Is it for STF or STL RPC mode? The first has TCP/HTTP layer and the latter on top of TCP/ZMQ&lt;/P&gt;&lt;P&gt;We are going to consolidate to STL-RPC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Hanoh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jan 2018 09:47:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/tools/how-api-client-authenticating-trex/m-p/3483842#M141</guid>
      <dc:creator>hhaim@cisco.com</dc:creator>
      <dc:date>2018-01-24T09:47:01Z</dc:date>
    </item>
    <item>
      <title>Re: How API Client authenticating TRex</title>
      <link>https://community.cisco.com/t5/tools/how-api-client-authenticating-trex/m-p/3483843#M142</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Our use case more into STF and test performed against transit devices (e.g. LoadBalancer/Firewall/etc)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jan 2018 10:05:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/tools/how-api-client-authenticating-trex/m-p/3483843#M142</guid>
      <dc:creator>riasudeen</dc:creator>
      <dc:date>2018-01-24T10:05:43Z</dc:date>
    </item>
  </channel>
</rss>

