I've taken another pass at the API and grouper implementation.
...
- I merged the common elements wiki into the standards and guidelines page
...
- I expanded on some sections there
...
- I implemented more things in the grouper implementation (including membershipType, returning a group member, better logging, etc), more documentation on the group/member wiki page
...
- There is a configuration-per-client so I can easily make changes to configuration per client without affecting other clients
...
- I added more usernames to the grouper demo server (same pass as before, usernames: test, test.subject.0, test.subject.1, etc up to 9)
...
- I added a SCIM setting to the grouper implementation, set it for test.subject.3, you can try it on the demo server
...
- Deployed latest code to the demo server
...
- Probably some other things don’t
...
- remember
e.g. in config file: /baseFolder/clients/test.subject.3/test.subject.3.properties
Code Block | ||||
---|---|---|---|---|
| ||||
############################# CONFIG FILE START ####################### |
...
# comma separated config files that override each other (files on the right override the left) |
...
# each should start with file: or classpath: |
...
# e.g. classpath:someFile.server.example.properties, file:c:/something/myconfig.properties |
...
tierClient.config.hierarchy = file:/opt/tomcats/tomcat_i/clients/common/baseClient.properties, file:/opt/tomcats/tomcat_i/clients/common/baseClientCustom.properties, file:/opt/tomcats/tomcat_i/clients/test.subject.3/test.subject.3.properties |
...
# this needs to be in each client config file |
...
# seconds between checking to see if the config files are updated |
...
tierClient.config.secondsBetweenUpdateChecks = 60 |
...
########################################
## Client config
########################################
# set this for a non helper config, which specifies which users it is applicable for, comma separated
...
######################################## ## Client config ######################################## # set this for a non helper config, which specifies which users it is applicable for, comma separated tierClient.users = test.subject.3 |
...
# if scim output can be used where applicable |
...
tierClient.scim = true |
...
########################################
## Get group member operation
########################################
...
######################################## ## Get group member operation ######################################## # show name in get group member: true, false, or inherit from tierClient.generic.showName |
...
tierClient.getGroupMember.showName = inherit |
...
############################# CONFIG FILE END ####################### |
Code Block | ||||
---|---|---|---|---|
| ||||
https://grouperdemo.internet2.edu/grouper-ws_v2_2/tierApiAuthz/v1/Groups/name:test:testGroup/Members/id:test?indent=true |
Output: (Granted this URL is not a SCIM url, but it shows the concept)
{
...
Code Block | ||||
---|---|---|---|---|
| ||||
{ "id":"test.subject.0", |
...
"meta":{ |
...
"location":" https://grouperdemo.internet2.edu/grouper-ws_v2_2/tierApiAuthz/v1/Groups/name:test:testGroup/Members/id:test.subject.0?indent=true", |
...
"resourceType":"User" |
...
}, |
...
"name":{ |
...
"formatted":"my name is test.subject.0" |
...
}, |
...
"schemas":[ |
...
"urn:ietf:params:scim:schemas:core:2.0:User" |
...
]
] } |
If people want to see something different or notice a bug or task please open a jira (Keith, we have a jira space right?)a JIRA issue. New users of the Internet2 JIRA will need to follow the 'sign up' link.
Thanks
Chris