...
- Logistics
- Leverage the Docker container provided by the COmanage team
- https://github.com/Internet2/comanage-registry-docker
- Includes
- Basic application on apache web server
- Shibboleth Service Provider
- Note for initial build build: export COMANAGE_REGISTRY_VERSION=3.0.0-rc1
- Pre-built containers in DockerHub - https://hub.docker.com/r/sphericalcowgroup/comanage-registry/https://hub.docker.com/r/sphericalcowgroup/comanage-registry-slapd/
- Initial version to use the Release Candidate versions: 3.0.0-rc1-shibboleth-sp/sphericalcowgroup/comanage-registry:3.0.0-rc1-shibboleth-sp
- Look at: https://github.com/Internet2/comanage-registry-docker/blob/master/docs/advanced-configuration.md for configuration options, examples, defaults, etc.
- Database – MARIA DB
- We will use the “TIER” MARIA DB container
- LDAP
- OpenLDAP
- Either the TIER OpenLDAP or COmanage OpenLDAP container will work
- The COmanage LDAP includes eduPerson and openssh-lpk.ldif (as does a version of the TIER LDAP)
- IdP/SP SAML Proxy
- We will use SATOSA
- Logging
- All logs will be sent to stdout using the TIER container logging definition.
- Leverage the Docker container provided by the COmanage team
- High Availability
- Typically done for the SAML proxy and LDAP only
- OpenLDAP (master/slave)
- Two SATOSA containers
- The early TIER distribution will not focus on this
- Typically done for the SAML proxy and LDAP only
- Post Install
- Send the users to a URL with “what is next”.
- TIER to draft site, COmanage team will help with the “what” is we can do the writing.
- Discussion - Demonstration/documentation of other provisioners
- TIER COmanage will leverage the LDAP provisioner
- TIER COmanage may provide some setup support for the Grouper provisioner
- TIER COmanage will likely provide no additional assistance for the other COmanage provisoners
- Github
- Home Directory (experimental – create homdirs on new user)
- Mailman
- Mediawiki (should we bundle this as a demo?)
- Changelog