comanage-dev - [comanage-dev] Collection of attributes during enrollment
Subject: COmanage Developers List
List archive
- From: Benn Oshrin <>
- To: comanage-dev <>
- Subject: [comanage-dev] Collection of attributes during enrollment
- Date: Mon, 17 Oct 2011 18:53:36 -0400
Broadly, there are three types of attributes we might be interested in collecting: Organizational, CO Person, and CO Person Role. Here's how I think we want to handle them during the enrollment/petition process:
- Org attributes are collect as configured by the CMP (ideally via
SAML or LDAP, but in practice via form for now).
- CO Person Role attributes are collected via form... these include
telephone numbers and extended attributes. Each enrollment petition
generates a new CO Person Role.
- CO Person attributes are treated as follows:
- Populate once: eg previous LIGO ID
- Populate once but allow change: eg preferred or author name
- Do not populate via form: eg: LIGO ID, @ligo.org email address
(these would get populated by some other process later)
Thoughts?
-Benn-
- [comanage-dev] Collection of attributes during enrollment, Benn Oshrin, 10/17/2011
- [comanage-dev] UI Accessibility, Benn Oshrin, 10/17/2011
- Message not available
- Re: [comanage-dev] Collection of attributes during enrollment, Benn Oshrin, 10/18/2011
- Re: [comanage-dev] Collection of attributes during enrollment, Scott Koranda, 10/23/2011
Archive powered by MHonArc 2.6.16.