...
You are required to use a container when running Grouper. This will ensure you have consistent directory structure, the correct version of libraries, and low risk and low effort upgrades. There are instructions to make using the container as easy as possible.
Expirable groups | Groups can have enabled / disabled dates and can be disabled (RBAC feature) |
|---|
| Container required | Grouper requires a container to run. No tarballs will be distributed.
No more patches, no more confusing upgrades, no more inconsistent environments, no more lengthy installs |
|---|
| Container redesign | One servlet container, easier mounts, one directory structure, fewer processes, maven build, patchless |
|---|
| Grouper installer installs container | Grouper installer wizard walks through running Grouper in container |
|---|
| Improve pagination in WS | Cursor based paging allows fewer memory problems and paging which does not skip records |
|---|
| Gantt chart for jobs | See when jobs have executed, job overlap, how long jobs take, success or error |
|---|
| Add new web services | Get audit log Web Service Add point in time options for WS get members, get groups, group save, get memberships |
|---|
| Attributes on memberships in UI | Allow direct and indirect attributes on memberships in UI (see JIRA). See wiki documentation here |
|---|
| WS and UI authentication | Basic authn stored in database. Passwordless WS authn in future. This is more friendly for containers |
|---|
| Simple custom UI | Analyze access for a policy. Allow easy join/leave. One-pager application |
|---|
| Automatic DDL upgrades | Grouper will can automatically adjust the database structure in a controlled way when a new container is run |
|---|
...