1. Switch to just using well known names. An example would be "All uPortal Users" for everyone, "All uPortal Channels" for all channels and "uPortal Administrators" for admins. Some effort would need to be done in the composite group store to prevent these groups from being created by users for security reasons which may be a bit of a road block.
2. Move the config into the database. A table could contain a known real id and the corresponding synthetic id of the designated group. This information could more easily be exported and would reduce the configuration tie to specific group keys.
Thoughts from any devs out there? -Eric Drew Wills wrote:
Eric,I updated dbunload,crn per our discussion on IRC: http://developer.ja-sig.org/source/changelog/jasigsvn/?cs=43464It still needs some attention, though...There are 3 rows defined in the UP_GROUP.default-data.xml file, each of which refers to an EntityType by Id: IPerson or IChannel. We either need to include a .default-data.xml file that defines these dependencies, or remove the need for 'Everyone', 'Portal Administrators', and 'All Channels' to have specific Ids.drew
smime.p7s
Description: S/MIME Cryptographic Signature
