Page History

...

The Subject API Diagnostics screen is an administrative screen for Grouper admins to troubleshoot and verify subject API sources.

This is on by default in a 2.3.0 patch or 2.3.1+.

...

Code Block

# should show subject api diagnostics?
uiV2.admin.subjectApiDiagnostics.show = true
 
# put in a group here if you want to allow the subject API diagnostics to certin users.  
# note, admins can always see the screen
uiV2.admin.subjectApiDiagnostics.must.be.in.group =

Run from GSH

If the UI doesnt start

grouper.properties (temporarily)

Code Block
gsh.exitOnSubjectCheckConfigProblem = false

if gsh doesnt start, try:

take source out of subject.properties
start gsh and get prompt
add source back in to subject.properties

run this in GSH

Code Block

GrouperSession.startRootSession();
edu.internet2.middleware.grouper.cache.GrouperCacheUtils.clearAllCaches();
GrouperUtil.assignField(edu.internet2.middleware.subject.provider.SourceManager.class, null, "manager", null, null);
-- continue below --

gsh

Code Block

GrouperSession.startRootSession();
new edu.internet2.middleware.grouper.grouperUi.serviceLogic.SubjectSourceDiagnostics().assignSourceId("SMUPerson_DEV").assignSubjectId("empl1").assignSubjectIdentifier("netid@school.edu").assignSearchString("em").subjectSourceDiagnosticsFromGsh()
===> 
SUCCESS: Found subject by id in 37ms: 'empl1'
         with SubjectFinder.findByIdAndSource("empl1", "SMUPerson_DEV", false)
SUCCESS: Subject id in returned subject matches the subject id searched for: 'empl1'
WARNING: No subject found by identifier in 14ms: 'netid@school.edu'
         with SubjectFinder.findByIdentifierAndSource("netid@school.edu", "SMUPerson_DEV", false)