comanage-dev - Re: [comanage-dev] bootstrap of COmanage CO and admin identifiers
Subject: COmanage Developers List
List archive
- From: Benn Oshrin <>
- To:
- Subject: Re: [comanage-dev] bootstrap of COmanage CO and admin identifiers
- Date: Wed, 29 Aug 2012 16:01:39 -0400
No. cm_identifiers is an MVPA Model (Multi-Valued Person Attribute), which can attach to an Org Identity or a CO Person [Role], but not both simultaneously.
Setup creates an org identity with the identifier that matches what you are logging in with. It then creates a co person, and links the org identity to it via cm_co_org_identity_links.
is not (by default) a CO identifier.
-Benn-
On 8/29/12 3:55 PM, Scott Koranda wrote:
Hi,
During the bootstrap process of the registry an org identifier
is created for the admin:
mysql> select * from cm_identifiers where id = 1\G
*************************** 1. row ***************************
id: 1
identifier:
type: uid
login: 1
status: A
co_person_id: NULL
org_identity_id: 1
created: 2012-08-29 08:19:24
modified: 2012-08-29 08:19:24
Shouldn't another row be created with that identifier value
and co_person_id linked to the id for the row
mysql> select * from cm_co_people where co_id = 1\G
*************************** 1. row ***************************
id: 1
co_id: 1
status: A
created: 2012-08-29 08:19:24
modified: 2012-08-29 08:19:24
?
Thanks,
Scott
- [comanage-dev] bootstrap of COmanage CO and admin identifiers, Scott Koranda, 08/29/2012
- Re: [comanage-dev] bootstrap of COmanage CO and admin identifiers, Benn Oshrin, 08/29/2012
- Re: [comanage-dev] bootstrap of COmanage CO and admin identifiers, Scott Koranda, 08/29/2012
- Re: [comanage-dev] bootstrap of COmanage CO and admin identifiers, Benn Oshrin, 08/29/2012
- Re: [comanage-dev] bootstrap of COmanage CO and admin identifiers, Scott Koranda, 08/29/2012
- Re: [comanage-dev] bootstrap of COmanage CO and admin identifiers, Benn Oshrin, 08/29/2012
Archive powered by MHonArc 2.6.16.