...
Command | Description | ||||
---|---|---|---|---|---|
addRootStem(extension, displayExtension) | Add top-level stem to the registry | ||||
addStem(parent stem name, extension, displayExtension) | Add stem to registry | ||||
delStem(stem name) | Delete stem from registry | ||||
obliterateStem(stem name, testOnlyBoolean, deleteFromPointInTimeBoolean) (Grouper v2.0.2+) | Delete stem, and subobjects. | ||||
getStemAttr(stem name, attr) | Get value of stem attribute | ||||
getStems(name) | Find all stems with a matching naming attribute value, returns a Set of stems | ||||
setStemAttr(stem name, attr, value) | Set value of stem attribute | ||||
StemFinder.findByName(grouperSession, name) | Find one stem by name | ||||
StemFinder.findByUuid(grouperSession, uuid) | Find one stem by uuid | ||||
Delete stem and subcontents |
| Delete stem and subcontents
Subjects
Command | Description | ||||
---|---|---|---|---|---|
addSubject(id, type, name) | Add local subject to registry. You need the jdbc source for this to work. The type parameter describes the type of subject (e.g. "people"), and is required non-null even though there are few useful api methods to query it. In 2.4.0.api.41+ patch, this will also create the id, name, description, and loginid attribute (unless grouper.properties create.attributes.when.creating.registry.subjects is false) | ||||
RegistrySubject.addOrUpdate(grouperSession, id, type, name, nameAttributeValue, loginid, description, email) | In 2.4.0.api.41+ patch, add a registry subject like addSubject, but specify the attribute values of name, loginid, etc e.g. RegistrySubject.addOrUpdate(grouperSession, "someTestSubject", "person", "Some Testsubject", "Name Some Test Subject", "stsub", "Some Testsubject - employee - also alumni", "some@test.subject"); | ||||
RegistrySubject.find(id, errorOnNotFound) | In 2.4.0.api.41+ patch, get a registry subject e.g. registrySubject = RegistrySubject.find("someTestSubject", false); | ||||
registrySubject.delete(grouperSession) | In 2.4.0.api.41+ patch, delete a registry subject e.g. registrySubject.delete(grouperSession); | ||||
RegistrySubjectAttribute.addOrUpdate(subjectId, attributeName, attributeValue) | In 2.4.0.api.41+ patch, add or update a registry subject attribute | ||||
registrySubjectAttribute.delete() | In 2.4.0.api.41+ patch, delete an attribute value | ||||
findSubject(idOrIdentifier) | Find a subject by id or identifier | ||||
findSubject(idOrIdentifier, type) | Find a subject by id or identifier; type is a deprecated parameter that is ignored | ||||
findSubject(idOrIdentifier, type, source) | Find a subject by id or identifier for a specific subject source; type is a deprecated parameter that is ignored | ||||
getSources() | Find all Subject sources | ||||
grouperSession = GrouperSession.startRootSession(); | Find all subjects in a source by search string | ||||
grouperSession = GrouperSession.startRootSession(); | Find a subject by id in a certain source | ||||
grouperSession = GrouperSession.startRootSession(); | Find a subject by identifier in a certain source | ||||
grouperSession = GrouperSession.startRootSession(); | Find a subject by id or identifier in a certain source | ||||
add test subjects to registry (e.g. test.subject.0 through 9) | grouperSession = GrouperSession.startRootSession(); | ||||
Edit subject (in this case name) | RegistrySubject registrySubject = GrouperDAOFactory.getFactory().getRegistrySubject().find("user1a", "person", true); | ||||
add a subject application principal with attributes (GSH) |
| ||||
remove a subject with attributes (GSH) |
| ||||
subject api diagnostics | grouper.properties (temporarily)
gsh
|
...