grouper-users - Re: [grouper-users] LDAP user source -> SOLVED ?
Subject: Grouper Users - Open Discussion List
List archive
- From: Lutz Suhrbier <>
- To: Tom Barton <>
- Cc:
- Subject: Re: [grouper-users] LDAP user source -> SOLVED ?
- Date: Tue, 11 Nov 2008 18:52:05 +0100
Hi Tom,
here you are !
If I comment out the four attribute elements in lines 148-151, then I get the "Error" information instead of the user name(s), wherever they may be listed.
I think it would be nice to have an option to map individual names to given source attributes to be shown to the user in the UI.
Regards
Lutz
I'm glad you've worked around the problem. Could you send me the <source> element for your LDAP source from your sources.xml?
Tom
Lutz Suhrbier wrote:
Hello,
meanwhile, I found a solution to that error.
Within the sources.xml, I have had to include at least those LDAP elements within "attribute" elements, which are requested in the subject, subjectId and description items of the source. If not, then the error described in my last posting (see below) occures.
As the wiki documentation states, that NOT including "attribute" elements just leads to requesting all available attributes from the given LDAP-source, this would mean that there is a bug in the implementation, or not ?
Or, is it a feature of the implementation, since looking through the documentation, I did not found a hint that Grouper-UI can be configured somewhere else as in sources.xml to define those attributes from the sources, which shall be presented to the user in the UI ?
<?xml version="1.0" encoding="utf-8"?> <!-- Grouper's subject resolver configuration $Id: sources.xml,v 1.8 2007/08/30 15:52:22 blair Exp $ --> <sources> <!-- Group Subject Resolver --> <!-- NOTE: It is recommended that you **not** change the default values for this source adapter. --> <source adapterClass="edu.internet2.middleware.grouper.GrouperSourceAdapter"> <id>g:gsa</id> <name>Grouper: Group Source Adapter</name> <type>group</type> </source> <!-- Group Subject Resolver --> <!-- <source adapterClass="edu.internet2.middleware.subject.provider.JDBCSourceAdapter"> <id>jdbc</id> <name>JDBC Source Adapter</name> <type>person</type> <init-param> <param-name>maxActive</param-name> <param-value>4</param-value> </init-param> <init-param> <param-name>maxIdle</param-name> <param-value>2</param-value> </init-param> <init-param> <param-name>maxWait</param-name> <param-value>5</param-value> </init-param> <init-param> <param-name>dbDriver</param-name> <param-value>org.hsqldb.jdbcDriver</param-value> </init-param> <init-param> <param-name>dbUrl</param-name> <param-value>jdbc:hsqldb:/root/grouper-api-1.3.1/dist/run/grouper;create=true</param-value> </init-param> <init-param> <param-name>dbUser</param-name> <param-value>sa</param-value> </init-param> <init-param> <param-name>dbPwd</param-name> <param-value></param-value> </init-param> <init-param> <param-name>SubjectID_AttributeType</param-name> <param-value>subjectId</param-value> </init-param> <init-param> <param-name>Name_AttributeType</param-name> <param-value>name</param-value> </init-param> <init-param> <param-name>Description_AttributeType</param-name> <param-value>name</param-value> </init-param> <search> <searchType>searchSubject</searchType> <param> <param-name>numParameters</param-name> <param-value>1</param-value> </param> <param> <param-name>sql</param-name> <param-value>select * from Subject where (subjectId=?)</param-value> </param> </search> <search> <searchType>searchSubjectByIdentifier</searchType> <param> <param-name>numParameters</param-name> <param-value>1</param-value> </param> <param> <param-name>sql</param-name> <param-value>select * from Subject where (name=?)</param-value> </param> </search> <search> <searchType>search</searchType> <param> <param-name>numParameters</param-name> <param-value>2</param-value> </param> <param> <param-name>sql</param-name> <param-value> select * from Subject where (subjectId like '%?%') or (name like '%?%') </param-value> </param> </search> </source> --> <!-- Example JNDI Person Resolver --> <source adapterClass="edu.internet2.middleware.subject.provider.JNDISourceAdapter"> <id>edit</id> <name>EDIT</name> <type>person</type> <init-param> <param-name>INITIAL_CONTEXT_FACTORY</param-name> <param-value>com.sun.jndi.ldap.LdapCtxFactory</param-value> </init-param> <init-param> <param-name>PROVIDER_URL</param-name> <param-value>ldap://localhost:389</param-value> </init-param> <init-param> <param-name>SECURITY_AUTHENTICATION</param-name> <param-value>simple</param-value> </init-param> <init-param> <param-name>SECURITY_PRINCIPAL</param-name> <param-value>cn=admin,dc=org</param-value> </init-param> <init-param> <param-name>SECURITY_CREDENTIALS</param-name> <param-value>u7secret</param-value> </init-param> <init-param> <param-name>SubjectID_AttributeType</param-name> <param-value>eduPersonPrincipalName</param-value> </init-param> <init-param> <param-name>Name_AttributeType</param-name> <param-value>cn</param-value> </init-param> <init-param> <param-name>Description_AttributeType</param-name> <param-value>mail</param-value> </init-param> <attribute>eduPersonPrincipalName</attribute> <attribute>cn</attribute> <attribute>eduPersonPrimaryAffiliation</attribute> <attribute>mail</attribute> <search> <searchType>searchSubject</searchType> <param> <param-name>filter</param-name> <param-value> (& (eduPersonPrincipalName=%TERM%)(objectclass=eduPerson)) </param-value> </param> <param> <param-name>scope</param-name> <param-value>SUBTREE_SCOPE</param-value> </param> <param> <param-name>base</param-name> <param-value>ou=developer,dc=e-taxonomy,dc=eu</param-value> </param> </search> <search> <searchType>searchSubjectByIdentifier</searchType> <param> <param-name>filter</param-name> <param-value> (& (eduPersonPrincipalName=%TERM%)(objectclass=eduPerson)) </param-value> </param> <param> <param-name>scope</param-name> <param-value>SUBTREE_SCOPE</param-value> </param> <param> <param-name>base</param-name> <param-value>ou=developer,dc=e-taxonomy,dc=eu</param-value> </param> </search> <search> <searchType>search</searchType> <param> <param-name>filter</param-name> <param-value> (& (|(mail=%TERM%)(cn=*%TERM%*)(eduPersonPrincipalName=%TERM%))(objectclass=eduPerson)) </param-value> </param> <param> <param-name>scope</param-name> <param-value>SUBTREE_SCOPE</param-value> </param> <param> <param-name>base</param-name> <param-value>ou=developer,dc=e-taxonomy,dc=eu</param-value> </param> </search> </source> </sources>
- LDAP user source, Lutz Suhrbier, 11/06/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Lutz Suhrbier, 11/10/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Tom Barton, 11/10/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Lutz Suhrbier, 11/11/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Tom Barton, 11/11/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Lutz Suhrbier, 11/12/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, GW Brown, Information Systems and Computing, 11/12/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Tom Barton, 11/12/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Lutz Suhrbier, 11/12/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Tom Barton, 11/11/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Lutz Suhrbier, 11/11/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Tom Barton, 11/12/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Lutz Suhrbier, 11/12/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Tom Barton, 11/12/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Lutz Suhrbier, 11/12/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Tom Barton, 11/10/2008
- Re: [grouper-users] LDAP user source -> SOLVED ?, Lutz Suhrbier, 11/10/2008
Archive powered by MHonArc 2.6.16.