Page History

...

The initial topology file we will start with doesn’t integrate with ActiveDirectory at all. Instead , it uses a capability of Shiro to embed users directly within its configuration. This approach is largely taken to “shake out” the process of editing topology files for various purposes. At the same time it minimizes external dependencies to help ensure a successful starting point. Now, create this topology file.

...

...

<GATEWAY_HOME>/conf/topologies/sample1.xml

...

...

<topology>
  <gateway>

    <provider>
      

...

<role>authentication</role>
      

...

<name>ShiroProvider</name>
      

...

<enabled>true</enabled>
      <param name="users.admin" value="admin-secret"/>
      <param name="urls./**" value="authcBasic"/>
    </provider>

  </gateway>
  <service>
    

...

<role>KNOX</role>
  </service>
</topology>

If you are a seasoned Knox veteran, you may notice the alternative <param name=“” value=“”/> style syntax. Both this and <param><name></name><value></value></param> style are supported. I’ve used the attribute style here for compactness.

...