- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
knox/Ldap integration
- Labels:
-
Apache Knox
-
Apache Ranger
Created ‎04-03-2018 07:27 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am trying to integrate Knox with Ldap but i have some doubts on the same .Please help me out . Please find below queries on the same :
1. I can see below property under /etc/knox/conf/topologies/admin.xml file
<role>authentication</role> <name>ShiroProvider</name> <enabled>true</enabled>
what is shiroProvider , can we customize it ? where does it exist ldap server end or knox ?
2. value of main.ldapRealm.contextFactory.authenticationMechanism is set to Simple and in documentation it is mentioned as well Apache Knox supports only simple authentication. What does it really mean , what is here contextFactory and main.ldapRealm.contextFactory.authenticationMechanism value simple ? what does simple refer to ?
3. urls./** : authcBasic
what does it really signify
I have gone through below link below but not much understanding , please help me on this .
https://developer.ibm.com/hadoop/2016/08/03/ldap-integration-with-apache-knox/
4. How to deny access to the user which is present already in the main.ldapRealm.userDnTemplate .
Thanks in advance
Created ‎04-05-2018 07:30 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Anurag Mishra LDAP authentication is configured by adding a "ShiroProvider" authentication provider to the cluster's topology file. When enabled, the Knox Gateway uses Apache Shiro (org.apache.shiro.realm.ldap.JndiLdapRealm
) to authenticate users against the configured LDAP store.
Please go through this document link
1. Shiro Provider is Knox side code and integrated. You need not worry about it's internal and change admin.xml (Admin topology) i.e. for Knox Administrators to proper LDAP/AD related values. For general usage, use default topology for services integration.
2. Read above documentation.
3. Read above documentation.
4. Make a group of users, you want to give access and whitelist them using ACL.
Created ‎04-04-2018 06:34 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Jay Kumar SenSharma
Hi jay could you please help me on this ?
Created ‎04-04-2018 06:57 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is the ultimate reference for knox. I am sure you will get the above questions answered with examples
Created ‎04-05-2018 07:26 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If your question got answered or resolved by that link please "Accept" and close this thread .
Thank you
Created ‎04-05-2018 07:30 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Anurag Mishra LDAP authentication is configured by adding a "ShiroProvider" authentication provider to the cluster's topology file. When enabled, the Knox Gateway uses Apache Shiro (org.apache.shiro.realm.ldap.JndiLdapRealm
) to authenticate users against the configured LDAP store.
Please go through this document link
1. Shiro Provider is Knox side code and integrated. You need not worry about it's internal and change admin.xml (Admin topology) i.e. for Knox Administrators to proper LDAP/AD related values. For general usage, use default topology for services integration.
2. Read above documentation.
3. Read above documentation.
4. Make a group of users, you want to give access and whitelist them using ACL.
