Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

Can you add a null source for that one?  Here is an example:

 

#########################################

## Configuration for source id: jdbc99

## Source configName: jdbc99

#########################################

subjectApi.source.jdbc99.id = jdbc99

 

# this is a friendly name for the source

subjectApi.source.jdbc99.name = jdbc99 is some legacy source that isnt used anymore

 

# the adapter class implements the interface: edu.internet2.middleware.subject.Source

# adapter class must extend: edu.internet2.middleware.subject.provider.BaseSourceAdapter

# edu.internet2.middleware.grouper.subj.GrouperJdbcSourceAdapter2  :  if doing JDBC this should be used if possible.  All subject data in one table/view.

# edu.internet2.middleware.grouper.subj.GrouperJdbcSourceAdapter   :  oldest JDBC source.  Put freeform queries in here

# edu.internet2.middleware.grouper.subj.GrouperJndiSourceAdapter   :  used for LDAP

# edu.internet2.middleware.subject.provider.NullSourceAdapter      :  returns not found.  You can use if you phase out a subject source

subjectApi.source.jdbc99.adapterClass = edu.internet2.middleware.subject.provider.NullSourceAdapter

 

# the 1st sort attribute for lists on screen that are derived from member table (e.g. search for member in group)

# you can have up to 5 sort attributes

subjectApi.source.jdbc99.param.sortAttribute0.value = WHATEVER

 

# the 1st search attribute for lists on screen that are derived from member table (e.g. search for member in group)

# you can have up to 5 search attributes

subjectApi.source.jdbc99.param.searchAttribute0.value = WHATEVER

 

 

From: [mailto:] On Behalf Of Black, Carey M.
Sent: Thursday, April 13, 2017 12:58 PM
To:
Subject: [grouper-users] RE: Subject API "lifecycle"/"interruption of service" issue....

 

Any input on this?

 

--

Carey Matthew

 

From: [] On Behalf Of Black, Carey M.
Sent: Tuesday, April 11, 2017 11:14 AM
To:
Subject: [grouper-users] Subject API "lifecycle"/"interruption of service" issue....

 

All,

 

I have stumbled into a behavior of Grouper that I think should be improved. For a several reasons. However, maybe I am not seeing some other designed way to deal with this condition.

 

The setup:

                I added a new Subject API to grouper. However, I knew it was “temporary” as I was just “trying it out”. ( Let’s call it “TEMP”.)

                I then removed the definition of the Subject API and now the Grouper UI is unable to display the memberships of any group that has any member from that TEMP Subject API.

                Error message when viewing a group in the New UI:

“

Error: Cant find source with id: 'TEMP', Possible source id's: 'g:gsa', 'grouperEntities', 'grouperExternal', 'jdbc', 'g:isa', , Problem calling method viewGroup on edu.internet2.middleware.grouper.grouperUi.serviceLogic.UiV2Group

“

( And no members of the group are displayed at all. )

 

 

 

While I doubt it would be common to add or remove Subject APIs. I am sure this kind of event is part of “the long lifecycle” of using Grouper.

 

From a conceptual point, I think it would be useful for Grouper to tolerate the “failed to find” and “failed to get data” from a Subject API to allow for a transition model between Subject API sources. Basically keep the “old references” while layering in the new (replacement) references to the new Subject API. If both Subject API’s (old and new) are available, then I think life is currently good. It is when the “old” is removed that it appears to impact, at least, the functionality of the UI.

 

 

Is there a way to tell grouper to “Just use the data you have” when the subject API is undefined? ( removed subject api definition)

Is there a way to tell grouper to “Just use the data you have” when the subject API fails to return data? (  intermittent incident/outage of Subject System )

Is there a way to give grouper a “dummy subject API configuration” that would just return the data that Grouper already has for the subject API?

 

Is there some documentation for “How to remove a Subject API” from Grouper that I did not yet find and follow?

Are there other ideas/details about adding/removing Subject API’s that I should be aware of?

 

Thanks in advance.

 

--

Carey Matthew