Security constraints are 'seeded' into the page.security file. Constraints are considered a part of the PSML definitions, and are included in the definition of a site. The roles, groups and users referenced in the page.security file must be included in the j2-seed.xml or be seeded into the database in some other way. If you are storing PSML in the database, the security constraints defined in page.security will be imported into the database along with all pages and folders.
-- David On Wed, Jul 24, 2013 at 9:57 AM, David Dyer <dd...@artifact-software.com>wrote: > I've looked over the deployment, build and admin documentation but haven't > found anything so I'll ask here. Can custom security constraint definitions > be defined in the j2-seed file so they're seeded into the initial jetspeed > db during the build? > > If so, what's the xml structure? > > thanks in advance. > > -- > David Dyer > Senior Integration Specialist > Artifact Software Inc > email: dd...@artifact-software.com > skype: ddyer1 > phone: 866-970-2435, ext 103. > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > jetspeed-user-unsubscribe@**portals.apache.org<jetspeed-user-unsubscr...@portals.apache.org> > For additional commands, e-mail: > jetspeed-user-help@portals.**apache.org<jetspeed-user-h...@portals.apache.org> > >
