Grouper Users - Open Discussion List

["Singley, Norman" <>]

Hi Folks.

 

I had to take a break from working on this, but I have time to get after it again.  I am having trouble, I think with getting all of the identity details from our openldap. I have grouper configured to authenticate through our CAS/Shib, and as far as I can tell, that’s working. 

 

When  I get to the UI, however, none of the members of my wheel group can create new folders.   I can add new members to the wheel group using the UI.

 

Next to the netid, there is an Entity not found error:

 

 

 

 

If I click on an identity, I get an “Error: cannot find subject” in a pink bar at the top of the page.

 

Playing around a bit, I tried going into the lite UI, and when I bring up the member details page I get this:

 

 

 

All three sources.xml files are the same, and attached. 

So, I’m not really sure where to go next.  Thanks for any help. 

 

 

Norman Singley

Directory Services

406 243 6799

 

 

<?xml version="1.0" encoding="utf-8"?>
<!--

    Copyright 2014 Internet2

    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
    You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.

-->
<!--
Grouper's subject resolver configuration
$Id: sources.example.xml,v 1.8 2009-08-11 20:18:09 mchyzer Exp $
-->

<sources>

  <!-- Group Subject Resolver -->
  
  <!-- 
     You can flag a source as not throwing exception on a findAll (general 
search) i.e. if it is
     ok if it is down.  Generally you probably won't want to do this.  It 
defaults to true if omitted.
  
     <init-param>
       <param-name>throwErrorOnFindAllFailure</param-name>
       <param-value>false</param-value>
     </init-param>
   -->
  
  <!-- 
      You can make virtual attributes (attributes with formatting or based on 
other attributes) like this:
      init-param name is subjectVirtualAttribute_<index>_<name> where index 
is the order to be processed
      if some depend on others (0 to 99).  The value is the jexl expression 
language.  You can use subjectUtils
      methods (aliased with "subjectUtils", or you can register your own 
class (must have default constructor).
      Here are examples:
  
     <init-param>
       <param-name>subjectVirtualAttribute_0_loginIdLfName</param-name>
       <param-value>Hey ${subject.getAttributeValue('LOGINID')} and 
${subject.getAttributeValue('LFNAME')}</param-value>
     </init-param>
     <init-param>
       <param-name>subjectVirtualAttribute_1_loginIdLfNameLoginId</param-name>
       <param-value>${subject.getAttributeValue('loginIdLfName')} Hey 
${subject.getAttributeValue('LOGINID')} and 
${subject.getAttributeValue('LFNAME')}</param-value>
     </init-param>
     <init-param>
       
<param-name>subjectVirtualAttributeVariable_JDBCSourceAdapterTest</param-name>
       
<param-value>edu.internet2.middleware.subject.provider.JDBCSourceAdapterTest</param-value>
     </init-param>
     <init-param>
       <param-name>subjectVirtualAttribute_2_loginIdSquared</param-name>
       
<param-value>${JDBCSourceAdapterTest.appendToSelf(subject.getAttributeValue('LOGINID'))}</param-value>
     </init-param>
  
    The first virtual attribute is accessible via: 
subject.getAttributeValue("loginIdLfNameLoginId");

    you can set these c3p0 settings: maxConnectionAge (seconds), 
testConnectionOnCheckout (true|false), 
       preferredTestQuery (e.g. select 1 from dual), idleConnectionTestPeriod 
(seconds)


     <init-param> 
       <param-name>findSubjectByIdOnCheckConfig</param-name> 
       <param-value>true|false</param-value> 
     </init-param> 
     <init-param> 
       <param-name>subjectIdToFindOnCheckConfig</param-name> 
       <param-value>someSubjectIdWhichMightExistOrWhatever</param-value> 
     </init-param> 

     <init-param> 
       <param-name>findSubjectByIdentifiedOnCheckConfig</param-name> 
       <param-value>true|false</param-value> 
     </init-param> 
     <init-param> 
       <param-name>subjectIdentifierToFindOnCheckConfig</param-name> 
       
<param-value>someSubjectIdentifierWhichMightExistOrWhatever</param-value> 
     </init-param> 

     <init-param> 
       <param-name>findSubjectByStringOnCheckConfig</param-name> 
       <param-value>true|false</param-value> 
     </init-param> 
     <init-param> 
       <param-name>stringToFindOnCheckConfig</param-name> 
       <param-value>someStringWhichMightExistOrWhatever</param-value> 
     </init-param>
   -->
  
  <!-- 
    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>

    <init-param>
      <param-name>subjectVirtualAttribute_0_searchAttribute0</param-name>
      
<param-value>${subject.getAttributeValue('name')},${subject.getAttributeValue('displayName')},${subject.getAttributeValue('alternateName')}</param-value>
    </init-param>
    <init-param>
      <param-name>sortAttribute0</param-name>
      <param-value>displayExtension</param-value>
    </init-param>
    <init-param>
      <param-name>searchAttribute0</param-name>
      <param-value>searchAttribute0</param-value>
    </init-param>
    <!-- on a findPage() this is the most results returned --> 
    <init-param>
      <param-name>maxPageSize</param-name>
      <param-value>100</param-value>
    </init-param>
    <internal-attribute>searchAttribute0</internal-attribute>
  </source>
  <!-- Group Subject Resolver -->

  <!-- 
    NOTE: It is recommended that you **not** change the default
          values for this source adapter.
  -->
  <source 
adapterClass="edu.internet2.middleware.grouper.entity.EntitySourceAdapter">
    <id>grouperEntities</id>
    <name>Grouper: Entity Source Adapter</name>
    <type>application</type>

    <init-param>
      <param-name>subjectVirtualAttribute_0_searchAttribute0</param-name>
      <!-- TODO add attribute for subject identifier -->
      
<param-value>${subject.getAttributeValue('name')},${subject.getAttributeValue('displayName')},${subject.getAttributeValue('alternateName')}</param-value>
    </init-param>
    <init-param>
      <param-name>sortAttribute0</param-name>
      <param-value>name</param-value>
    </init-param>
    <init-param>
      <param-name>searchAttribute0</param-name>
      <param-value>searchAttribute0</param-value>
    </init-param>
    <internal-attribute>searchAttribute0</internal-attribute>
  </source>
  <!-- Entity Subject Resolver -->

 <source 
adapterClass="edu.internet2.middleware.grouper.subj.GrouperJdbcSourceAdapter">
    <id>jdbc</id>
    <name>Example JDBC Source Adapter</name>
     <type>person</type>
     
     <!-- 
edu.internet2.middleware.subject.provider.C3p0JdbcConnectionProvider (default)
          
edu.internet2.middleware.subject.provider.DbcpJdbcConnectionProvider (legacy) 
          edu.internet2.middleware.grouper.subj.GrouperJdbcConnectionProvider 
            (same settings as grouper.hibernate.properties, the driver, url, 
pass, maxActive, maxIdle, maxWait are forbidden -->
     <init-param>
       <param-name>jdbcConnectionProvider</param-name>
       
<param-value>edu.internet2.middleware.grouper.subj.GrouperJdbcConnectionProvider
 </param-value>
     </init-param>
     
     <!-- If using emails and need email addresses in sources, set which 
attribute has the email address in this source -->
     <init-param>
       <param-name>emailAttributeName</param-name>
       <param-value>email</param-value>
     </init-param>
     
     <!-- if more than this many results are returned, then throw a too many 
subjects exception -->
     <init-param>
       <param-name>maxResults</param-name>
       <param-value>1000</param-value>
     </init-param>

    <!-- on a findPage() this is the most results returned --> 
    <init-param>
      <param-name>maxPageSize</param-name>
      <param-value>100</param-value>
    </init-param>

     <!-- note: again, if you use GrouperJdbcConnectionProvider, then you 
should not fill out maxActive, maxIdle,
       maxWait, dbDriver, dbUrl, dbUser, dbPwd, since it will use the 
grouper.hibernate.properties db settings -->

     <!--   init-param>
       <param-name>maxActive</param-name>
       <param-value>16</param-value>
     </init-param>
     <init-param>
       <param-name>maxIdle</param-name>
       <param-value>16</param-value>
     </init-param>
     <init-param>
       <param-name>maxWait</param-name>
       <param-value>-1</param-value>
     </init-param -->
     
     <!--      
       e.g. mysql:           com.mysql.jdbc.Driver
       e.g. p6spy (log sql): com.p6spy.engine.spy.P6SpyDriver
         for p6spy, put the underlying driver in spy.properties
       e.g. oracle:          oracle.jdbc.driver.OracleDriver
       e.g. hsqldb:          org.hsqldb.jdbcDriver
       e.g. postgres:        org.postgresql.Driver -->

     <!-- init-param>
       <param-name>dbDriver</param-name>
       <param-value>org.hsqldb.jdbcDriver</param-value>
     </init-param -->
     
     <!-- 
       e.g. mysql:           jdbc:mysql://localhost:3306/grouper
       e.g. p6spy (log sql): [use the URL that your DB requires]
       e.g. oracle:          jdbc:oracle:thin:@server.school.edu:1521:sid
       e.g. hsqldb (a):      jdbc:hsqldb:dist/run/grouper;create=true
       e.g. hsqldb (b):      jdbc:hsqldb:hsql://localhost:9001
       e.g. postgres:        jdbc:postgresql:grouper -->
     
     <!-- init-param>
       <param-name>dbUrl</param-name>
       
<param-value>jdbc:hsqldb:C:/projects/GrouperI2MI_1-2/grouper/dist/run/grouper</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>id</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>description</param-value>
     </init-param>
     <init-param>
       <param-name>subjectVirtualAttribute_0_searchAttribute0</param-name>
       
<param-value>${subject.name},${subjectUtils.defaultIfBlank(subject.getAttributeValue('LFNAME'),
 "")},${subjectUtils.defaultIfBlank(subject.getAttributeValue('LOGINID'), 
"")},${subjectUtils.defaultIfBlank(subject.description, 
"")},${subjectUtils.defaultIfBlank(subject.getAttributeValue('EMAIL'), 
"")}</param-value>
     </init-param>
     <init-param>
       <param-name>sortAttribute0</param-name>
       <param-value>LFNAME</param-value>
     </init-param>
     <init-param>
       <param-name>sortAttribute1</param-name>
       <param-value>LOGINID</param-value>
     </init-param>
     <init-param>
       <param-name>searchAttribute0</param-name>
       <param-value>searchAttribute0</param-value>
     </init-param>
     <internal-attribute>searchAttribute0</internal-attribute>
     
     <!-- if you are going to use the inclause attribute
       on the search to make the queries batchable when searching
       by id or identifier -->
     <init-param>
       <param-name>useInClauseForIdAndIdentifier</param-name>
       <param-value>true</param-value>
     </init-param>
     
     <!-- comma separate the identifiers for this row, this is for the 
findByIdentifiers if using an in clause -->
     <init-param>
       <param-name>identifierAttributes</param-name>
       <param-value>LOGINID</param-value>
     </init-param>

     <!-- subject identifier to store in grouper's member table -->
     <init-param>
       <param-name>subjectIdentifierAttribute0</param-name>
       <param-value>LOGINID</param-value>
     </init-param>

     <search>
         <searchType>searchSubject</searchType>
         <param>
             <param-name>sql</param-name>
             <param-value>
select
   s.subjectid as id, s.name as name,
   (select sa2.value from subjectattribute sa2 where name='name' and 
sa2.SUBJECTID = s.subjectid) as lfname,
   (select sa3.value from subjectattribute sa3 where name='loginid' and 
sa3.SUBJECTID = s.subjectid) as loginid,
   (select sa4.value from subjectattribute sa4 where name='description' and 
sa4.SUBJECTID = s.subjectid) as description,
   (select sa5.value from subjectattribute sa5 where name='email' and 
sa5.SUBJECTID = s.subjectid) as email
from
   subject s
where
   {inclause}
            </param-value>
         </param>
         <param>
             <param-name>inclause</param-name>
             <param-value>
s.subjectid = ?
            </param-value>
         </param>
     </search>
     <search>
         <searchType>searchSubjectByIdentifier</searchType>
         <param>
             <param-name>sql</param-name>
             <param-value>
select
   s.subjectid as id, s.name as name,
   (select sa2.value from subjectattribute sa2 where name='name' and 
sa2.SUBJECTID = s.subjectid) as lfname,
   (select sa3.value from subjectattribute sa3 where name='loginid' and 
sa3.SUBJECTID = s.subjectid) as loginid,
   (select sa4.value from subjectattribute sa4 where name='description' and 
sa4.SUBJECTID = s.subjectid) as description,
   (select sa5.value from subjectattribute sa5 where name='email' and 
sa5.SUBJECTID = s.subjectid) as email
from
   subject s, subjectattribute a
where
   a.name='loginid' and s.subjectid = a.subjectid and {inclause}
             </param-value>
         </param>
         <param>
             <param-name>inclause</param-name>
             <param-value>
   a.value = ? 
            </param-value>
         </param>
     </search>
     <search>
        <searchType>search</searchType>
         <param>
             <param-name>sql</param-name>
             
             <!--  for postgres, use this query since no concat() exists:
             
             select
   subject.subjectid as id, subject.name as name,
   lfnamet.lfname as lfname, loginidt.loginid as loginid,
   desct.description as description, emailt.email as email
from
   subject
   left join (select subjectid, value as lfname from subjectattribute
     where name='name') lfnamet
     on subject.subjectid=lfnamet.subjectid
   left join (select subjectid, value as loginid from subjectattribute
     where name='loginid') loginidt
     on subject.subjectid=loginidt.subjectid
   left join (select subjectid, value as description from subjectattribute
      where name='description') desct
     on subject.subjectid=desct.subjectid
   left join (select subjectid, value as email from subjectattribute
      where name='email') emailt
     on subject.subjectid=emailt.subjectid
where
   (lower(name) like '%' || ? || '%')
   or (lower(lfnamet.lfname) like '%' || ? || '%')
   or (lower(loginidt.loginid) like '%' || ? || '%')
   or (lower(desct.description) like '%' || ? || '%')
   or (lower(emailt.email) like '%' || ? || '%')
             
for SQL-server:

select
   subject.subjectid as id, subject.name as name,
   lfnamet.lfname as lfname, loginidt.loginid as loginid,
   desct.description as description, emailt.email as email
from
   subject
   left join (select subjectid, value as lfname from subjectattribute
     where name='name') lfnamet
     on subject.subjectid=lfnamet.subjectid
   left join (select subjectid, value as loginid from subjectattribute
     where name='loginid') loginidt
     on subject.subjectid=loginidt.subjectid
   left join (select subjectid, value as description from subjectattribute
      where name='description') desct
     on subject.subjectid=desct.subjectid
   left join (select subjectid, value as email from subjectattribute
      where name='email') emailt
     on subject.subjectid=emailt.subjectid
where
   (lower(name) like '%' + ? + '%')
   or (lower(lfnamet.lfname) like '%' + ? + '%')
   or (lower(loginidt.loginid) like '%' + ? + '%')
   or (lower(desct.description) like '%' + ? + '%')
   or (lower(emailt.email) like '%' + ? + '%')

              -->
             
             <param-value>
select
   s.subjectid as id, s.name as name,
   (select sa2.value from subjectattribute sa2 where name='name' and 
sa2.SUBJECTID = s.subjectid) as lfname,
   (select sa3.value from subjectattribute sa3 where name='loginid' and 
sa3.SUBJECTID = s.subjectid) as loginid,
   (select sa4.value from subjectattribute sa4 where name='description' and 
sa4.SUBJECTID = s.subjectid) as description,
   (select sa5.value from subjectattribute sa5 where name='email' and 
sa5.SUBJECTID = s.subjectid) as email
from 
   subject s
where
   s.subjectid in (
      select subjectid from subject where lower(name) like 
concat('%',concat(?,'%')) union
      select subjectid from subjectattribute where searchvalue like 
concat('%',concat(?,'%'))
   )
             </param-value>
         </param>
     </search>
   </source>
   
   <!--  
    <!- - This is an alternate jdbc source which allows for more complex 
searches, assumes 
      all data is in one table or view, and that all attributes are single 
valued.  There are
      not queries to configure in sources.xml - - >
    <source 
adapterClass="edu.internet2.middleware.grouper.subj.GrouperJdbcSourceAdapter2">
    <id>sourceId</id>
    <name>Source name</name>
     <type>person</type>
     <init-param>
       <param-name>jdbcConnectionProvider</param-name>
       
<param-value>edu.internet2.middleware.grouper.subj.GrouperJdbcConnectionProvider</param-value>
     </init-param>

     <init-param>
       <param-name>maxResults</param-name>
       <param-value>1000</param-value>
     </init-param>

      <init-param>
       <param-name>dbTableOrView</param-name>
       <param-value>person_source_v</param-value>
     </init-param>
      <init-param>
       <param-name>subjectIdCol</param-name>
       <param-value>some_id</param-value>
     </init-param>
     <init-param>
       <param-name>nameCol</param-name>
       <param-value>name</param-value>
     </init-param>
     <init-param>
       <param-name>descriptionCol</param-name>
       <param-value>description</param-value>
     </init-param>
     <init-param>
       <!- - search col where general searches take place, lower case - - >
       <param-name>lowerSearchCol</param-name>
       <param-value>description_lower</param-value>
     </init-param>
     <init-param>
       <!- - optional col if you want the search results sorted in the API 
(note, UI might override) - - >
       <param-name>defaultSortCol</param-name>
       <param-value>description</param-value>
     </init-param>
     <init-param>
       <!- - col which identifies the row, perhaps not subjectId, add 
multiple by incrementing the 0 index - - >
       <param-name>subjectIdentifierCol0</param-name>
       <param-value>pennname</param-value>
     </init-param>
     <init-param>
       <!- - col which identifies the row, perhaps not subjectId, add 
multiple by incrementing the 0 index - - >
       <param-name>subjectIdentifierCol1</param-name>
       <param-value>penn_id</param-value>
     </init-param>
     <!- - now you can count up from 0 to N of attributes for various cols.  
          The name is how to reference in subject.getAttribute() - - >
     <init-param>
       <param-name>subjectAttributeCol0</param-name>
       <param-value>pennname</param-value>
     </init-param>
     <init-param>
       <param-name>subjectAttributeName0</param-name>
       <param-value>PENNNAME</param-value>
     </init-param>
     <init-param>
       <param-name>subjectAttributeCol1</param-name>
       <param-value>description_lower</param-value>
     </init-param>
     <init-param>
       <param-name>subjectAttributeName1</param-name>
       <param-value>searchAttribute0</param-value>
     </init-param>
     <init-param>
       <param-name>sortAttribute0</param-name>
       <param-value>description</param-value>
     </init-param>
     <init-param>
       <param-name>searchAttribute0</param-name>
       <param-value>searchAttribute0</param-value>
     </init-param>
     <internal-attribute>searchAttribute0</internal-attribute>
     <!- - ##########################  STATUS SECTION for searches to filter 
out inactives and allow
                                                     the user to filter by 
status with e.g. status=all
                                                     this is optional, and 
advanced - -> 
     <!- - column or attribute which represents the status - - >
     <!- -
     <init-param>
       <param-name>statusDatastoreFieldName</param-name>
       <param-value>status</param-value>
     </init-param> - - >
     <!- - search string from user which represents the status.  e.g. 
status=active - - >
     <!- -
     <init-param>
       <param-name>statusLabel</param-name>
       <param-value>status</param-value>
     </init-param> - - >
     <!- - available statuses from screen (if not specified, any will be 
allowed). comma separated list.
          Note, this is optional and you probably dont want to configure it, 
it is mostly necessary
          when you have multiple sources with statuses...  if someone types 
an invalid status
          and you have this configured, it will not filter by it - - >
     <!- - 
     <init-param>
       <param-name>statusesFromUser<param-name>
       <param-value>Active, Inactive, Pending, All</param-value>
     </init-param> - - >
     <!- - all label from the user - - >
     <!- -
     <init-param>
       <param-name>statusAllFromUser</param-name>
       <param-value>All</param-value>
     </init-param> - - >
     <!- - if no status is specified, this will be used (e.g. for active 
only).  Note, the value should be of the
          form the user would type in - - >
     <!- - 
     <init-param>
       <param-name>statusSearchDefault</param-name>
       <param-value>status=active</param-value>
     </init-param> - - >
     <!- - translate between screen values of status, and the data store 
value.  Increment the 0 to 1, 2, etc for more translations.
          so the user could enter: status=active, and that could translate to 
status_col=A.  The 'user' is what the user types in,
          the 'datastore' is what is in the datastore.  The user part is not 
case-sensitive.  Note, this could be a many to one - - >
     <!- -
     <init-param>
       <param-name>statusTranslateUser0</param-name>
       <param-value>active</param-value>
     </init-param>
     <init-param>
       <param-name>statusTranslateDatastore0</param-name>
       <param-value>A</param-value>
     </init-param> - - >
     <!- - ########################## END STATUS SECTION - - > 
   </source>
   -->
   
   
  <source 
adapterClass="edu.internet2.middleware.grouper.subj.GrouperJndiSourceAdapter">
    <id>oid</id>
    <name>Open Ldap Directory</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://cidp.umt.edu: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>uid=grouperquery,ou=people,dc=umt,dc=edu</param-value>
    </init-param>
    <init-param>
      <param-name>SECURITY_CREDENTIALS</param-name>
      <param-value>password</param-value>
    </init-param>
     <init-param>
      <param-name>SubjectID_AttributeType</param-name>
      <param-value>uid</param-value>
    </init-param>
     <init-param>
      <param-name>SubjectID_formatToLowerCase</param-name>
      <param-value>false</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>cn</param-value>
    </init-param>

    <init-param>
      <param-name>VTLDAP_VALIDATOR</param-name>
      <param-value>CompareLdapValidator</param-value>
    </init-param>
    <init-param>
      <param-name>VTLDAP_VALIDATOR_COMPARE_DN</param-name>
      <param-value>ou=people,dc=umt,dc=edu</param-value>
    </init-param>
    <init-param>
      <param-name>VTLDAP_VALIDATOR_COMPARE_SEARCH_FILTER_STRING</param-name>
      <param-value>ou=people</param-value>
    </init-param>
    
    /// Scope Values can be: OBJECT_SCOPE, ONELEVEL_SCOPE, SUBTREE_SCOPE 
    /// For filter use 
    
    <search>
        <searchType>searchSubject</searchType>
        <param>
            <param-name>filter</param-name>
            <param-value>
                (&amp; (umid=%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=people,dc=umt,dc=edu
            </param-value>
        </param>
         
    </search>
    <search>
        <searchType>searchSubjectByIdentifier</searchType>
        <param>
            <param-name>filter</param-name>
            <param-value>
                (&amp; (uid=%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=people,dc=umt,dc=edu
            </param-value>
        </param>
    </search>
    
    <search>
       <searchType>search</searchType>
         <param>
            <param-name>filter</param-name>
            <param-value>
                (&amp; 
(|(|(uid=%TERM%)(cn=*%TERM%*))(umid=%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=people,dc=umt,dc=edu
            </param-value>
        </param>
    </search>
    <init-param>
      <param-name>subjectVirtualAttribute_0_searchAttribute0</param-name>
      
<param-value>${subjectUtils.defaultIfBlank(subject.getAttributeValueOrCommaSeparated('uid'),
 
"")},${subjectUtils.defaultIfBlank(subject.getAttributeValueOrCommaSeparated('cn'),
 
"")},${subjectUtils.defaultIfBlank(subject.getAttributeValueOrCommaSeparated('exampleEduRegId'),
 "")}</param-value>
    </init-param>
    <init-param>
      <param-name>sortAttribute0</param-name>
      <param-value>cn</param-value>
    </init-param>
    <init-param>
      <param-name>searchAttribute0</param-name>
      <param-value>searchAttribute0</param-value>
    </init-param>

         <!--
     <!- - ##########################  STATUS SECTION for searches to filter 
out inactives and allow
                                                     the user to filter by 
status with e.g. status=all
                                                     this is optional, and 
advanced - -> 
     <!- - column or attribute which represents the status - - >
     <!- -
     <init-param>
       <param-name>statusDatastoreFieldName</param-name>
       <param-value>status</param-value>
     </init-param> - - >
     <!- - search string from user which represents the status.  e.g. 
status=active - - >
     <!- -
     <init-param>
       <param-name>statusLabel</param-name>
       <param-value>status</param-value>
     </init-param> - - >
     <!- - available statuses from screen (if not specified, any will be 
allowed). comma separated list.
          Note, this is optional and you probably dont want to configure it, 
it is mostly necessary
          when you have multiple sources with statuses...  if someone types 
an invalid status
          and you have this configured, it will not filter by it - - >
     <!- - 
     <init-param>
       <param-name>statusesFromUser<param-name>
       <param-value>Active, Inactive, Pending, All</param-value>
     </init-param> - - >
     <!- - all label from the user - - >
     <!- -
     <init-param>
       <param-name>statusAllFromUser</param-name>
       <param-value>All</param-value>
     </init-param> - - >
     <!- - if no status is specified, this will be used (e.g. for active 
only).  Note, the value should be of the
          form the user would type in - - >
     <!- - 
     <init-param>
       <param-name>statusSearchDefault</param-name>
       <param-value>status=active</param-value>
     </init-param> - - >
     <!- - translate between screen values of status, and the data store 
value.  Increment the 0 to 1, 2, etc for more translations.
          so the user could enter: status=active, and that could translate to 
status_col=A.  The 'user' is what the user types in,
          the 'datastore' is what is in the datastore.  The user part is not 
case-sensitive.  Note, this could be a many to one - - >
     <!- -
     <init-param>
       <param-name>statusTranslateUser0</param-name>
       <param-value>active</param-value>
     </init-param>
     <init-param>
       <param-name>statusTranslateDatastore0</param-name>
       <param-value>A</param-value>
     </init-param> - - >
     <!- - ########################## END STATUS SECTION - - > 
        -->

    <internal-attribute>searchAttribute0</internal-attribute>

    ///Attributes you would like to display when doing a search 
    <attribute>cn</attribute>
    <attribute>sn</attribute>
    <attribute>uid</attribute>
    <attribute>department</attribute>
    <attribute>umid</attribute>

    <!-- subject identifier to store in grouper's member table -->
    <init-param>
      <param-name>subjectIdentifierAttribute0</param-name>
      <param-value>uid</param-value>
    </init-param>
   
  </source>


</sources>

INFO: Server startup in 51567 ms
Dec 01, 2016 10:47:38 AM org.apache.tomcat.util.http.Parameters 
processParameters
INFO: Invalid chunk starting at byte [12] and ending at byte [12] with a 
value of [null] ignored
Dec 01, 2016 10:47:41 AM org.apache.tomcat.util.http.Parameters 
processParameters
INFO: Invalid chunk starting at byte [16] and ending at byte [16] with a 
value of [null] ignored
Dec 01, 2016 10:47:49 AM org.apache.tomcat.util.http.Parameters 
processParameters
INFO: Invalid chunk starting at byte [19] and ending at byte [19] with a 
value of [null] ignored
Dec 01, 2016 2:33:15 PM org.apache.tomcat.util.http.Parameters 
processParameters
INFO: Invalid chunk starting at byte [0] and ending at byte [0] with a value 
of [null] ignored
Dec 02, 2016 11:19:23 AM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Dec 02, 2016 11:19:24 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Dec 02, 2016 11:19:24 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper-ws] appears to have started a thread 
named [Timer-0] but has failed to stop it. This is very likely to create a 
memory leak.
Dec 02, 2016 11:19:24 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper-ws] appears to have started a thread 
named [Timer-1] but has failed to stop it. This is very likely to create a 
memory leak.
Dec 02, 2016 11:19:24 AM org.apache.catalina.loader.WebappClassLoader 
clearThreadLocalMap
SEVERE: The web application [/grouper-ws] created a ThreadLocal with key of 
type [org.apache.axiom.util.UIDGenerator$1] (value 
[org.apache.axiom.util.UIDGenerator$1@56bb6bef]) and a value of type [long[]] 
(value [[J@2aab4465]) but failed to remove it when the web application was 
stopped. This is very likely to create a memory leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper] appears to have started a thread named 
[Timer-3] but has failed to stop it. This is very likely to create a memory 
leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper] appears to have started a thread named 
[C3P0PooledConnectionPoolManager[identityToken->2sa7j09kdpyh9k1tlr5gb|45987154]-AdminTaskTimer]
 but has failed to stop it. This is very likely to create a memory leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper] appears to have started a thread named 
[C3P0PooledConnectionPoolManager[identityToken->2sa7j09kdpyh9k1tlr5gb|45987154]-HelperThread-#0]
 but has failed to stop it. This is very likely to create a memory leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper] appears to have started a thread named 
[C3P0PooledConnectionPoolManager[identityToken->2sa7j09kdpyh9k1tlr5gb|45987154]-HelperThread-#1]
 but has failed to stop it. This is very likely to create a memory leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper] appears to have started a thread named 
[C3P0PooledConnectionPoolManager[identityToken->2sa7j09kdpyh9k1tlr5gb|45987154]-HelperThread-#2]
 but has failed to stop it. This is very likely to create a memory leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper] appears to have started a thread named 
[Thread-35] but has failed to stop it. This is very likely to create a memory 
leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper] appears to have started a thread named 
[Thread-36] but has failed to stop it. This is very likely to create a memory 
leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper] appears to have started a thread named 
[Thread-37] but has failed to stop it. This is very likely to create a memory 
leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearThreadLocalMap
SEVERE: The web application [/grouper] created a ThreadLocal with key of type 
[net.sf.json.AbstractJSON.CycleSet] (value 
[net.sf.json.AbstractJSON$CycleSet@19647f0]) and a value of type 
[java.lang.ref.SoftReference] (value [java.lang.ref.SoftReference@314cde60]) 
but failed to remove it when the web application was stopped. This is very 
likely to create a memory leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearThreadLocalMap
SEVERE: The web application [/grouper] created a ThreadLocal with key of type 
[net.sf.json.AbstractJSON.CycleSet] (value 
[net.sf.json.AbstractJSON$CycleSet@19647f0]) and a value of type 
[java.lang.ref.SoftReference] (value [java.lang.ref.SoftReference@2d9b89e9]) 
but failed to remove it when the web application was stopped. This is very 
likely to create a memory leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearThreadLocalMap
SEVERE: The web application [/grouper] created a ThreadLocal with key of type 
[net.sf.json.AbstractJSON.CycleSet] (value 
[net.sf.json.AbstractJSON$CycleSet@19647f0]) and a value of type 
[java.lang.ref.SoftReference] (value [java.lang.ref.SoftReference@3e7b3763]) 
but failed to remove it when the web application was stopped. This is very 
likely to create a memory leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearThreadLocalMap
SEVERE: The web application [/grouper] created a ThreadLocal with key of type 
[net.sf.json.AbstractJSON.CycleSet] (value 
[net.sf.json.AbstractJSON$CycleSet@19647f0]) and a value of type 
[java.lang.ref.SoftReference] (value [java.lang.ref.SoftReference@b7164a1]) 
but failed to remove it when the web application was stopped. This is very 
likely to create a memory leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearThreadLocalMap
SEVERE: The web application [/grouper] created a ThreadLocal with key of type 
[net.sf.json.AbstractJSON.CycleSet] (value 
[net.sf.json.AbstractJSON$CycleSet@19647f0]) and a value of type 
[java.lang.ref.SoftReference] (value [java.lang.ref.SoftReference@41858be5]) 
but failed to remove it when the web application was stopped. This is very 
likely to create a memory leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearThreadLocalMap
SEVERE: The web application [/grouper] created a ThreadLocal with key of type 
[net.sf.json.AbstractJSON.CycleSet] (value 
[net.sf.json.AbstractJSON$CycleSet@19647f0]) and a value of type 
[java.lang.ref.SoftReference] (value [java.lang.ref.SoftReference@26a388fe]) 
but failed to remove it when the web application was stopped. This is very 
likely to create a memory leak.
Dec 02, 2016 11:19:25 AM org.apache.catalina.loader.WebappClassLoader 
clearThreadLocalMap
SEVERE: The web application [/grouper] created a ThreadLocal with key of type 
[java.lang.InheritableThreadLocal] (value 
[java.lang.InheritableThreadLocal@3a76ef83]) and a value of type 
[edu.internet2.middleware.grouper.j2ee.GrouperRequestWrapper] (value 
[edu.internet2.middleware.grouper.j2ee.GrouperRequestWrapper@6b6de007]) but 
failed to remove it when the web application was stopped. This is very likely 
to create a memory leak.
Dec 02, 2016 11:19:26 AM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
Dec 02, 2016 11:19:29 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal 
performance in production environments was not found on the 
java.library.path: 
/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Dec 02, 2016 11:19:30 AM org.apache.tomcat.util.digester.SetPropertiesRule 
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting 
property 'mapperContextRootRedirectEnabled' to 'true' did not find a matching 
property.
Dec 02, 2016 11:19:30 AM org.apache.tomcat.util.digester.SetPropertiesRule 
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting 
property 'mapperDirectoryRedirectEnabled' to 'true' did not find a matching 
property.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
Dec 02, 2016 11:19:30 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Dec 02, 2016 11:19:30 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1125 ms
Dec 02, 2016 11:19:30 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Dec 02, 2016 11:19:30 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.35
Grouper starting up: version: 2.3.0, build date: 2016/04/16 05:37:21, env: 
<no label configured>
grouper.properties read from: 
/grouper/grouper.ui-2.3.0/dist/grouper/WEB-INF/classes/grouper.properties
Grouper current directory is: /grouper/apache-tomcat-6.0.35/bin
log4j.properties read from:   
/grouper/grouper.ui-2.3.0/dist/grouper/WEB-INF/classes/log4j.properties
Grouper is logging to file:   
/grouper/apache-tomcat-6.0.35/logs/grouperUi/grouper_error.log, at min level 
WARN for package: edu.internet2.middleware.grouper, based on log4j.properties
grouper.hibernate.properties: 
/grouper/grouper.ui-2.3.0/dist/grouper/WEB-INF/classes/grouper.hibernate.properties
grouper.hibernate.properties: 
grouper@jdbc:oracle:thin:@griz06.umt.edu:7456:grouper
problem with sources
Couldnt startup grouper: Error initializing SourceManager
java.lang.RuntimeException: Error initializing SourceManager
        at 
edu.internet2.middleware.subject.provider.SourceManager.init(SourceManager.java:322)
        at 
edu.internet2.middleware.subject.provider.SourceManager.<init>(SourceManager.java:252)
        at 
edu.internet2.middleware.subject.provider.SourceManager.getInstance(SourceManager.java:262)
        at 
edu.internet2.middleware.grouper.misc.GrouperStartup.startup(GrouperStartup.java:225)
        at 
edu.internet2.middleware.grouper.ui.GrouperUiFilter.init(GrouperUiFilter.java:800)
        at 
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:295)
        at 
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
        at 
org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
        at 
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4072)
        at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:4726)
        at 
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
        at 
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
        at 
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
        at 
org.apache.catalina.core.StandardService.start(StandardService.java:525)
        at 
org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
Caused by: java.lang.RuntimeException: Problem reading sources xml file: 
classpath:sources.xml
        at 
edu.internet2.middleware.subject.provider.SourceManager.parseConfig(SourceManager.java:391)
        at 
edu.internet2.middleware.subject.provider.SourceManager.init(SourceManager.java:319)
        ... 22 more
Caused by: org.xml.sax.SAXParseException; lineNumber: 609; columnNumber: 19; 
The entity name must immediately follow the '&' in the entity reference.
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown 
Source)
        at org.apache.commons.digester.Digester.parse(Digester.java:1666)
        at 
edu.internet2.middleware.subject.provider.SourceManager.parseConfig(SourceManager.java:388)
        ... 23 more
Dec 02, 2016 11:19:38 AM org.apache.catalina.core.StandardContext start
SEVERE: Error filterStart
Dec 02, 2016 11:19:38 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [/grouper] startup failed due to previous errors
Dec 02, 2016 11:20:10 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper] appears to have started a thread named 
[Resource Destroyer in BasicResourcePool.close()] but has failed to stop it. 
This is very likely to create a memory leak.
Dec 02, 2016 11:20:11 AM org.apache.catalina.startup.HostConfig 
deployDescriptor
INFO: Deploying configuration descriptor host-manager.xml
Dec 02, 2016 11:20:11 AM org.apache.catalina.startup.HostConfig 
deployDescriptor
INFO: Deploying configuration descriptor manager.xml
Dec 02, 2016 11:20:12 AM org.apache.catalina.startup.HostConfig 
deployDirectory
INFO: Deploying web application directory ROOT
Dec 02, 2016 11:20:12 AM org.apache.catalina.startup.HostConfig 
deployDirectory
INFO: Deploying web application directory docs
Dec 02, 2016 11:20:12 AM org.apache.catalina.startup.HostConfig 
deployDirectory
INFO: Deploying web application directory examples
Dec 02, 2016 11:20:12 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Dec 02, 2016 11:20:12 AM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Dec 02, 2016 11:20:12 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/118  config=null
Dec 02, 2016 11:20:12 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 42244 ms
Dec 02, 2016 11:22:20 AM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Dec 02, 2016 11:22:21 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Dec 02, 2016 11:22:21 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper-ws] appears to have started a thread 
named [Timer-0] but has failed to stop it. This is very likely to create a 
memory leak.
Dec 02, 2016 11:22:21 AM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/grouper-ws] appears to have started a thread 
named [Timer-1] but has failed to stop it. This is very likely to create a 
memory leak.
Dec 02, 2016 11:22:21 AM org.apache.catalina.loader.WebappClassLoader 
clearThreadLocalMap
SEVERE: The web application [/grouper-ws] created a ThreadLocal with key of 
type [org.apache.axiom.util.UIDGenerator$1] (value 
[org.apache.axiom.util.UIDGenerator$1@2f2c36a3]) and a value of type [long[]] 
(value [[J@7fb71f86]) but failed to remove it when the web application was 
stopped. This is very likely to create a memory leak.
Dec 02, 2016 11:22:21 AM org.apache.catalina.core.StandardContext stop
INFO: Container 
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/grouper] has 
not been started
Dec 02, 2016 11:22:21 AM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
Dec 02, 2016 11:22:25 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal 
performance in production environments was not found on the 
java.library.path: 
/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Dec 02, 2016 11:22:25 AM org.apache.tomcat.util.digester.SetPropertiesRule 
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting 
property 'mapperContextRootRedirectEnabled' to 'true' did not find a matching 
property.
Dec 02, 2016 11:22:25 AM org.apache.tomcat.util.digester.SetPropertiesRule 
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting 
property 'mapperDirectoryRedirectEnabled' to 'true' did not find a matching 
property.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
Dec 02, 2016 11:22:26 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Dec 02, 2016 11:22:26 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1124 ms
Dec 02, 2016 11:22:26 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Dec 02, 2016 11:22:26 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.35
Grouper starting up: version: 2.3.0, build date: 2016/04/16 05:37:21, env: 
<no label configured>
grouper.properties read from: 
/grouper/grouper.ui-2.3.0/dist/grouper/WEB-INF/classes/grouper.properties
Grouper current directory is: /grouper/apache-tomcat-6.0.35/bin
log4j.properties read from:   
/grouper/grouper.ui-2.3.0/dist/grouper/WEB-INF/classes/log4j.properties
Grouper is logging to file:   
/grouper/apache-tomcat-6.0.35/logs/grouperUi/grouper_error.log, at min level 
WARN for package: edu.internet2.middleware.grouper, based on log4j.properties
grouper.hibernate.properties: 
/grouper/grouper.ui-2.3.0/dist/grouper/WEB-INF/classes/grouper.hibernate.properties
grouper.hibernate.properties: 
grouper@jdbc:oracle:thin:@griz06.umt.edu:7456:grouper
sources.xml read from:        
/grouper/grouper.ui-2.3.0/dist/grouper/WEB-INF/classes/sources.xml
sources.xml groupersource id: g:gsa
sources.xml ldap source id:   oid: 
uid=grouperquery,ou=people,dc=umt,dc=edu@ldap://cidp.umt.edu:389
sources.xml groupersource id: grouperEntities
sources.xml jdbc source id:   jdbc: GrouperJdbcConnectionProvider
Grouper error: grouper versions do not match, GrouperVersion.class: 2.3.0, 
grouper.version.properties: 2.3.0, manifest: null
Dec 02, 2016 11:23:06 AM org.apache.catalina.startup.HostConfig 
deployDescriptor
INFO: Deploying configuration descriptor host-manager.xml
Dec 02, 2016 11:23:06 AM org.apache.catalina.startup.HostConfig 
deployDescriptor
INFO: Deploying configuration descriptor manager.xml
Dec 02, 2016 11:23:06 AM org.apache.catalina.startup.HostConfig 
deployDirectory
INFO: Deploying web application directory ROOT
Dec 02, 2016 11:23:06 AM org.apache.catalina.startup.HostConfig 
deployDirectory
INFO: Deploying web application directory docs
Dec 02, 2016 11:23:06 AM org.apache.catalina.startup.HostConfig 
deployDirectory
INFO: Deploying web application directory examples
Dec 02, 2016 11:23:06 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Dec 02, 2016 11:23:07 AM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Dec 02, 2016 11:23:07 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/141  config=null
Dec 02, 2016 11:23:07 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 41136 ms
Dec 02, 2016 11:24:14 AM org.apache.tomcat.util.http.Parameters 
processParameters
INFO: Invalid chunk starting at byte [0] and ending at byte [0] with a value 
of [null] ignored