Date: Thu, 28 Mar 2024 14:26:39 +0000 (UTC) Message-ID: <1450474626.6517.1711635999483@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6516_1702392579.1711635999480" ------=_Part_6516_1702392579.1711635999480 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
As of COmanage Registry v1.0.0, whether or not Organizational Identities= are pooled must be decided at setup time, and once set cannot be changed. = For more information on which setting you should select, see Organizational Ident= ity Pooling.
If you are worried that you may select the wrong setting, you should pro= bably be setting up a development instance first so that you can mock up yo= ur data to see how you would like it to operate. That way, if you made the = wrong choice you can just "throw away" the development instance and try aga= in.
Decide whether or not to pool organizational identities before proceedin= g.
As of COmanage Registry v3.1.0, new installations can not be configured = with Org Identity Pooling. Support for Org Identity Pooling will be removed= in v5.0.0 (CO-1470).
Run the Registry configuration script. Be sure to enter the username tha=
t will be returned by your web server's authentication engine. For example,=
under Apache this corresponds to $REMOTE_USER
.
Be careful with file ownerships here. You will need to run this command =
as the web server user or as root, depending on whether or not the web serv=
er user can write files to the application directory (which is normally a b=
ad idea). If running as root, make sure the cache directory (wherever app/tmp
points to) and all of its subdirectories and files are writ=
eable by the web server. chown -R
and chgrp -R
ma=
y be in order.
$ cd ap= p $ ./Console/cake setup Enter administrator's given name > Pat Enter administrator's family name > Lee Enter administrator's login username > plee@university.edu Enable organizational identity pooling? (Yes/No)=20 [No] > No
setup
is intended to be run once. After you run it, you sho=
uld be able to login via the web interface and make whatever changes you ne=
ed that way. If you need to run it again, the easiest approach is to drop t=
he database and start over.
When running this step under v0.9.4, you may notice deprecation messages= like
Deprecated (16384): Validation::notEmpty() is deprecated.
These messages may be safely ignored, and do not affect other versions (=
CO-1119).
Under certain circumstances, it may be desirable to run the setup script= non-interactively, for example as part of an automated installation proces= s. As of v1.0.1, this is possible by passing command line flags to the setu= p shell. Note that all flags listed here must be passed for a= completely non-interactive setup. Any missing flags will result in a promp= t for the required value.
--admin-given-name
: Given name of initial administrator
--admin-family-name
: Family name of initial adm=
inistrator--admin-username
: Administrator's username, as descr=
ibed above--enable-pooling
: Whether or not to enable organizat=
ional pooling, as described above =E2=80=93 this must match the langua=
ge key 'fd.yes'
in order to enable pooling (which by defa=
ult will be the literal string Yes
, case sensitive)$ cd ap= p $ ./Console/cake setup --admin-given-name Pat --admin-family-name "Jones Sm= ith" --admin-username "pat.jones.smith@university.edu" --enable-pooling=3DY= es