...
Release | Item | Description |
|---|---|---|
| 2.4 | Refine next generation provisioning | Take PSPNG and feedback from the field and add more features, refine it, improve it, etc |
| 2.4? | Add new messaging strategies | Add new messaging strategies in the Grouper Messaging system for ActiveMQ, RabbitMQ, Azure, AMQP, others? |
| 2.4? | Administrative configuration UI | User interface for administration and configuration of Grouper (include PSPNG) |
| 2.4? | Grouper loader real time updates | Allow a change log table (SQL triggers) or messages to trigger loader updates for a partial population or single user |
| 2.4 | Grouper instrumentation | Improve and standardize Grouper logging to provide centralized metrics at an institution and the ability to upload stats to a central Internet2 server |
| 2.4 | TIER packaging for 2.4 | In the TIER packaging for Grouper, create Grouper docker container, integrate Grouper with Shibboleth, configure PSPNG, configure user registration with COManage |
| 2.4 | Revise build environment and dependency retrieval | Revising code environment to get rid of dependencies and the hybrid builds (Maven and ant builds, hard to keep everything in sync) Possible options:
Need to figure out versions for each dependency. |
| 2.4 (tentative) | upgrade vt-ldap | to ldaptive (PSPNG to use ldaptive) |
| 2.4? | Add remaining attribute/permission operations to WS | Add permission hierarchy services for roles, actions. Limits? Any other attribute permission services? |
| 2.4 | UI accessibility | Incorporate recommendations from Colorado UI accessibility review |
Not yet assigned | Improve gsh by adding readline like capabilities (line editing, tab completions, history, etc). Explore incorporating Jline2 into the current beanshell approach or possibly adopting groovysh as the base. | |
2.4 | Use a message bus to notify interested parties, including traditional provisioning agents, of group changes. TBD: supported message transports, format of messages, content of messages. Possible transports include AWS, Azure, ActiveMQ. | |
2.4? | Finish the new UI, replace admin and lite UI | Add features into the new Grouper 2.2 UI so that everything from the admin UI and the lite UI can be performed in the new UI. Remove the admin and lite UIs (redirect outdated links). Add user based auditing and overall auditing. Add new features like the ability to easily configure "rules" in the UI |
| 2.4? | Improve pagination in WS | Return the total count |
| 2.4Not yet assigned | UI warn, restrict, or schedule large operations | If adding a group to another group, maybe warn, restrict, notify user that the operation will take a while to provision. Or schedule this for later? |
On-going | Grouper Core enhancement | Continue adding capabilities to meet requirements from the field. |
On-going | Community contributions | Solicit and publicize community contributions of extensions and complements to Grouper. |
Not yet assigned | Register for notifications | Add ability for users to register to be notified of changes to specified objects. Note, there are rules to email users about changes to memberships |
| 2.4?Not yet assigned | Expire dates | Add expire dates to groups (other objects? attribute definitions? attribute names?) and expose privilege expire dates to WS/UI |
2.4 | More provisioning connectors | Add further connectors to reflect specified group, membership, role, and permission information into external systems and services. Include Google provisioning (from the Unicon contribution to the PSPNG)2.4 (tentative) |
Not yet assigned | Scaling REST webservice | A page in the Administration guide, Grouper always available web services and client, demonstrates one way to provide always available services using a specialized client. The CIFER REST web service will need the server-side capability to provide that always-available functionality. In addition the REST API should be able to access multiple, read-only caches so it can efficiently handle any increase in query requests, most of which will not need to directly access the primary database. PSPNG should be able to provision to a database table, and WS should be able to read from that table (or tables) for simple operations. |
| Not yet assigned yet | Inbound messages | Allow Grouper to read a message queue and act on messages (e.g. membership changes etc) |
...