...
- Planning
- Install/Test/Roll-out
- Developing Integration Materials
| Info |
|---|
Note that as of 2019, the preferred Grouper installation approach is using Grouper 2.5+ installation requires using a container. See the InCommon Trusted Access Platform (ITAP) Docker Containers. |
I - Planning Stage
Gain a basic understanding of Grouper
- Review Grouper introductory/overview documentation, including the glossary.
- The "Grouper Training for Managers" video series provides an overview of both access management at large, as well as Grouper's core concepts and features
- Take Grouper School training
- Review the Grouper Deployment Guide Review the TIER Grouper Deployment Guide (as of October 2019, being updated on the wiki here)
- Imagine how you expect Grouper to fit into your identity and application architecture
- Check out the Grouper Demo
- Install Grouper in a test environment to familiarize yourself with Grouper.
...
- Review InCommon Trusted Access Platform Docker Containers. This is the suggested installation as of 2019 and required as of Grouper 2.5 and above.
- What Grouper environments will you initially install? A development instance? A test (Q/A) instance? A production instance? All three or just one or two?
- For your software environments, what host machines will you run on? What ports will be used, what firewall settings might need to be made?
- Will you run Grouper software "as root" or as another user?
- How will you handle authentication to the UI and to Web Services?
Plan groups data hierarchy and naming
...
- What database (existing or new) will form your Grouper database repository?
- What database (existing) will provide you with subject data
- Do you plan to replicate groups data out to LDAP or some other database? (for LDAP, see this training video)
- Do you plan to automate groups management (for some or all groups) based on one or more data sources (and using the Grouper Loader)?
- Should you use just an application server or an application server + web server to enable web access?
- Which interfaces to groups data do plan to initially implement and support? Web browser access? Web services access? Grouper shell access?
- How do you expect end-users and applications to interface for read-only and for read-write purposes to groups data? See this training video on integration
- Security considerations (e.g. wheel group, externalizing and encrypting database/ldap passwords)
- How will you structure configuration files?
- Will you use
II - Installation, Testing, Rollout
...
- Confirm access to hardware/software environments, data sources and destinations
- Outline steps for installation and configuration of Grouper software elements. Consider using this quickstart method
- Finalize initial stems/folders to create, authentication approach, initial groups to create and populate (see examples)
- consider using the template wizard
- Plan basic testing of functionality
- Plan for ongoing operations, considering your desired approach to such duties as
- Monitoring / Management / Maintenance (see the section on Ongoing Admin Tasks)
- Support for Application developers/managers integrating their apps with Grouper
- Support for any end-users
- Plan to document your installation and configuration as you go along. Please share your experience so other sites can benefit.
...
See Also
Grouper Training VideosSchool training
Grouper Training slides (including group naming best practices)
...