Reply To: Authentication Problem with Knox

Are you integrating a federation provider? I assume you’re playing with a demo/sandbox environment?

Was comparing my testing knox topology with yours and I don’t have federation at all.


<topology>

<gateway>

<provider>
<role>authentication</role>
<name>ShiroProvider</name>
<enabled>true</enabled>
<param>
<name>sessionTimeout</name>
<value>30</value>
</param>
<param>
<name>main.ldapRealm</name>
<value>org.apache.hadoop.gateway.shirorealm.KnoxLdapRealm</value>
</param>
<param>
<name>main.ldapRealm.userDnTemplate</name>
<value>uid={0},ou=people,dc=hadoop,dc=apache,dc=org</value>
</param>
<param>
<name>main.ldapRealm.contextFactory.url</name>
<value>ldap://687843-node1.dsrax.com:33389</value>
</param>
<param>
<name>main.ldapRealm.contextFactory.authenticationMechanism</name>
<value>simple</value>
</param>
<param>
<name>urls./**</name>
<value>authcBasic</value>
</param>
</provider>

<provider>
<role>identity-assertion</role>
<name>Default</name>
<enabled>true</enabled>
</provider>

<provider>
<role>authorization</role>
<name>AclsAuthz</name>
<enabled>true</enabled>
</provider>

</gateway>

<service> ...

My test string I’m using command


curl -i -k -u admin:admin-password -X GET “https://localhost:8443/gateway/default/webhdfs/v1/?op=GETHOMEDIRECTORY”