Skip to Content.
Sympa Menu

grouper-users - [grouper-users] subject API diagnostics

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] subject API diagnostics


Chronological Thread 
  • From: "Hyzer, Chris" <>
  • To: " Mailing List" <>
  • Subject: [grouper-users] subject API diagnostics
  • Date: Tue, 24 Jan 2017 09:07:48 +0000
  • Accept-language: en-US
  • Authentication-results: spf=none (sender IP is ) ;
  • Ironport-phdr: 9a23:Af1oNBRlsf/VADbpk4z43fgNfdpsv+yvbD5Q0YIujvd0So/mwa6zbBWN2/xhgRfzUJnB7Loc0qyN4vymBDRLuM3Z+Fk5M7V0HycfjssXmwFySOWkMmbcaMDQUiohAc5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aFRrwLxd6KfroEYDOkcu3y/qy+5rOaAlUmTaxe71/IRG5oAnLtsQanYRuJrs/xxfVv3BFZ/lYyWR0KFyJgh3y/N2w/Jlt8yRRv/Iu6ctNWrjkcqo7ULJVEi0oP3g668P3uxbDSxCP5mYHXWUNjhVIGQnF4wrkUZr3ryD3q/By2CiePc3xULA0RTGv5LplRRP0lCsKMSMy/WfKgcJyka1bugqsqRxhzYDJfIGbOvlwfqLBctwVXmdBRNpdWzBbD4+gc4cDEewMNvtYoYnnoFsOqAOzCQeuCuLvyz5HmGX20bUn2Ok/EQHGxg0gH8kAvH/Jq9j1MbsdUeC1zajJ0zrDdehb2Tbm6IfUaBwhvOmMUqx2ccrX00UgCR7KjkiJpIHjIjib2OMNs22B4OphU+Kik2wnpBxqrTez3MssjJPGhocLxVzc7SV22pw1Kse9SEJhZ96rCp5QuD+CO4t0X8wtWH1ntDw7yrIbv5OwYSsEyIw/yhLBcfOLb5WE7xf+WOqMPDt1gXxldb2jixqu9EWtyPPzW8au31tPqydJjMXAum0V2xDO5MWLVuFx80O81TqVyQzf9+VJLVopmafZKpMsxKM7mIAJvkTZBCD2nV37jK+IeUUg/eil8/zpb6nhqJOAOYJ4kxzzPaYwlsCmBuQ3KRYBU3Kc+eShyL3s5kr5QKhMjvIriKXZqIraJcMHpqGnHwBVzocj6xG5Dzu819QYgGUHLFZCeBKAjIjlIU3BIPf9DfunglSslilkx+zeM7H/GJrBMmXPnbL8cbpg9kJRzQQzwN9D655ID7wMIuz8V0Dru9HdCxI1LRC4z/v/BNV4zIweWGaPAqGDMKPVtF+F/ucvLPWMZI4VuTfyNeIl6uXvjX8ihVARZ7Sp3YMJZ3C+GPRqOVuWbmfxgtsZC2cFohI+TPD2iF2FSTNTaGyyX6Uh5jEjFo2mF57PRp22gLOfxie7BYZbZmRHClCXDXfobJuIV+0NaCKUPs9ujCYEVb6/RI89yx2irhH1xKd6LrmcxipN/53508Vt6veWiAo/7ydcDsKB3nuLQn0u2G4EWncT1aF7oEpygnOCyrQyy6hXD9tO//5TFxohOITH5+18F93oXA/dJJGEREvwEfu8BjRkBPIg0dIUJw5WG8+jlVqLiy+hA64HmqajBYc/tL/E0n73Yctx1iCVh+Eak1A6T54XZiWdjall+l2LCg==
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

I am working on an admin tool in the UI which would help set up subject sources and identify problems with them.

 

I would like to add a section that shows what subjects look like in the UI in various places (and why).

 

Any comments or anything else you would like to see?

 

Thanks

Chris

 

 

 

Here is the full report (note passwords are not displayed, only admins can see the link and page):

 

SUCCESS: Found subject by id in 12ms: 'test.subject.0'

         with SubjectFinder.findByIdAndSource("test.subject.0", "jdbc", false)

SUCCESS: Subject id in returned subject matches the subject id searched for: 'test.subject.0'

WARNING: No subject found by identifier in 1ms: 'test.subject.0.id'

         with SubjectFinder.findByIdentifierAndSource("test.subject.0.id", "jdbc", false)

SUCCESS: Found 10 subjects by search string in 2ms: 'test'

         with SubjectFinder.findAll("test.subject.0.id", "jdbc")

SUCCESS: Found 10 subjects by paged search string in 2ms: 'test'

         with SubjectFinder.findPage("test.subject.0.id", "jdbc")

 

######## SUBJECT ATTRIBUTES ########

 

Subject id: test.subject.0 with subject.getId()

  - the subject id should be an unchanging opaque identifier

  - the subject id is stored in the grouper_members table

Subject name: my name is test.subject.0 with subject.getName()

  - the subject name is generally first last

Subject description: description.test.subject.0 with subject.getDescription()

  - the subject description can have more info such as the id, name, dept, etc

Subject type: person with subject.getTypeName()

  - the subject type is not really used

Subject attribute 'subjectid' has 1 value: 'test.subject.0'

 - with subject.getAttributeValue("subjectid")

Subject attribute 'name' has 1 value: 'my name is test.subject.0'

  - with subject.getAttributeValue("name")

Subject attribute 'lfname' has 1 value: 'name.test.subject.0'

  - with subject.getAttributeValue("lfname")

Subject attribute 'loginid' has 1 value: 'id.test.subject.0'

  - with subject.getAttributeValue("loginid")

Subject attribute 'description' has 1 value: 'description.test.subject.0'

  - with subject.getAttributeValue("description")

Subject attribute 'email' has 1 value: ''

  - with subject.getAttributeValue("email")

 

######## SOURCE CONFIGURATION ########

 

Adapter class: 'edu.internet2.middleware.grouper.subj.GrouperJdbcSourceAdapter'

  - configured in subject.properties: subjectApi.source.jdbc.adapterClass

SUCCESS: Found adapter class

SUCCESS: Instantiated adapter class

Source id: 'jdbc'

  - configured in subject.properties: subjectApi.source.jdbc.id

Source name: 'Example JDBC Source Adapter'

  - configured in subject.properties: subjectApi.source.jdbc.name

Source types: 'person'

  - configured in subject.properties: subjectApi.source.jdbc.types

Source param name: 'Name_AttributeType' has value: 'name'

  - configured in subject.properties: subjectApi.source.jdbc.param.Name_AttributeType.value

Source param name: 'subjectIdentifierAttribute0' has value: 'LOGINID'

  - configured in subject.properties: subjectApi.source.jdbc.param.subjectIdentifierAttribute0.value

Source param name: 'maxResults' has value: '1000'

  - configured in subject.properties: subjectApi.source.jdbc.param.maxResults.value

Source param name: 'jdbcConnectionProvider' has value: 'edu.internet2.middleware.grouper.subj.GrouperJdbcConnectionProvider'

  - configured in subject.properties: subjectApi.source.jdbc.param.jdbcConnectionProvider.value

Source param name: 'identifierAttributes' has value: 'LOGINID'

  - configured in subject.properties: subjectApi.source.jdbc.param.identifierAttributes.value

Source param name: 'sortAttribute0' has value: 'LFNAME'

  - configured in subject.properties: subjectApi.source.jdbc.param.sortAttribute0.value

Source param name: 'sortAttribute1' has value: 'LOGINID'

  - configured in subject.properties: subjectApi.source.jdbc.param.sortAttribute1.value

Source param name: 'Description_AttributeType' has value: 'description'

  - configured in subject.properties: subjectApi.source.jdbc.param.Description_AttributeType.value

Source param name: 'subjectVirtualAttribute_0_searchAttribute0' has value: '${subject.name},${subjectUtils.defaultIfBlank(subject.getAttributeValue('LFNAME'), "")},${subjectUtils.defaultIfBlank(subject.getAttributeValue('LOGINID'), "")},${subjectUtils.defaultIfBlank(subject.description, "")},${subjectUtils.defaultIfBlank(subject.getAttributeValue('EMAIL'), "")}'

  - configured in subject.properties: subjectApi.source.jdbc.param.subjectVirtualAttribute_0_searchAttribute0.value

Source param name: 'useInClauseForIdAndIdentifier' has value: 'true'

  - configured in subject.properties: subjectApi.source.jdbc.param.useInClauseForIdAndIdentifier.value

Source param name: 'SubjectID_AttributeType' has value: 'id'

  - configured in subject.properties: subjectApi.source.jdbc.param.SubjectID_AttributeType.value

Source param name: 'searchAttribute0' has value: 'searchAttribute0'

  - configured in subject.properties: subjectApi.source.jdbc.param.searchAttribute0.value

Source param name: 'maxPageSize' has value: '100'

  - configured in subject.properties: subjectApi.source.jdbc.param.maxPageSize.value

Source param name: 'emailAttributeName' has value: 'email'

  - configured in subject.properties: subjectApi.source.jdbc.param.emailAttributeName.value

Internal attributes: 'searchAttribute0'

  - configured in subject.properties: subjectApi.source.jdbc.internalAttributes

No attributes configured

Search 'searchSubject' param name: 'sql' has 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}'

  - configured in subject.properties: subjectApi.source.jdbc.search.searchSubject.param.sql.value

Search 'searchSubject' param name: 'inclause' has value: 's.subjectid = ?'

  - configured in subject.properties: subjectApi.source.jdbc.search.searchSubject.param.inclause.value

Search 'searchSubjectByIdentifier' param name: 'sql' has 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}'

  - configured in subject.properties: subjectApi.source.jdbc.search.searchSubjectByIdentifier.param.sql.value

Search 'searchSubjectByIdentifier' param name: 'inclause' has value: 'a.value = ?'

  - configured in subject.properties: subjectApi.source.jdbc.search.searchSubjectByIdentifier.param.inclause.value

Search 'search' param name: 'sql' has 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(?,'%'))    )'

  - configured in subject.properties: subjectApi.source.jdbc.search.search.param.sql.value

 

 



  • [grouper-users] subject API diagnostics, Hyzer, Chris, 01/24/2017

Archive powered by MHonArc 2.6.19.

Top of Page