CMP enrollment configuration
- Although the data model permits multiple CMP enrollment configurations to be defined, COmanage Registry currently only permits one active configuration for the platform.
- There is no REST interface to this table since it is intended to configure the COmanage Registry UI.
- CO enrollment flows are handled via cm_co_enrollment_flows.
integer, primary key
Should CMP enrollment attempt to pull attributes from an organizational LDAP server before prompting for attributes?
If the enrollee must authenticate, should CMP enrollment attempt to extract attributes from a SAML assertion before prompting for attributes?
Should organizational identity attributes be extracted from the server environment? (eg: those that might be set by the web server auth module.)
Should CO enrollment flows be able to prompt for organizational identity attributes? (These attributes will be considered less authoritative than if they had been obtained via LDAP or SAML.)
Should organizational identities be pooled and made available to all COs on the CMP?
See CO-193 for additional information
Do enrollees need to have a sponsor to enroll?
Do enrollees need to have a sponsor to stay enrolled?
|eds_help_url||varchar(256)||For the Shibboleth Embedded Discovery Service, the help URL to publish|
|eds_preferred_idps||text(4000)||For the Shibboleth Embedded Discovery Service, the entityIds to always show (one per line)|
|eds_hidden_idps||text(4000)||For the Shibboleth Embedded Discovery Service, the entityIds to hide (one per line)|
Only one CMP configuration may be active