By default, GAC remains disabled. Therefore, even after upgrading to Connect 2.9.3 product will continue to use existing permission model. However, for new and existing customers, enabling GAC can bring some changes.
New Customers
Key Considerations for GAC Planning
- Identify Custom Roles and Responsibilities
- Create a Permission Model matrix needed
- If LDAP is integrated then identify Groups and Roles for LDAP based on permission Model
Existing Customers
Existing customers would need to go through planning process for desired security model and this will also involve migrating existing objects and entities to the new model
- Create Inventory of existing objects, assets, roles, projects and groups in the Adeptia prescribed templates
- Create a target state permission model as per Adeptia supplied templates
- Use the GAC guidelines to migrate exiting model to the target state model
