This article will provide a framework to follow when upgrading Identity Panel and other suite components to version 7.
Identity Panel
Providers - no changes are required to existing providers. However, Panel Connections are now available for user.
HyperSync
The configuration for HyperSync will work without any changes being made to the configuration. However, there are some necessary synchronization steps to consider.
- A full synchronization of HyperSync has to be run to repopulate and join Hyperverse objects.
- Any attributes sourced only in the Hyperverse in v6 will need to be scripted.
- Create a report from the v6 Hyperverse. Utilize a Load Fixture to repopulate attributes in v7.
- Delete any old Hypersync synchronization schedules.
- Disable Delta Sync
- Add a Manual Sync Schedule
- Reload Graph
- HyperSync Sync
- Projected Silo Sync
- Campaign Sync
- Request Sync
- Reload Identity Graph
- Synchronize a single user and check for errors
- Execute HyperSync Sync.
- Perform a Silo Reindex
- Verify that searches include Hyperverse objects in TimeTraveler.
- Lookup Definitions
- Create a join for each Lookup Definition that exists.
- The Join Rule can be as simple as location|DN|DN
- Apply Join Rules
- This will allow the Lookup Definitions to be included in the Join Graph that resides in memory.
Test Panel
No changes required unless Panel Connections will be used.
Service Panel
There are multiple updates that are required for Service Panel to operate in v7.
- Theme - initialize a light theme
- Projected Silo
- Check name and object type after upgrade.
- Self Claim - update to match groups defined in roles
- Silo Data
- List Join Graphs that will contribute to a Projected Silo.
- Reference Attributes can be used. (AzureAD: manager)
- Audience - the filters must return a matching string for the Audience rule to evaluate to True. Alternately, the filters can be left blank if the specified role has unfiltered access.
- Id Filter - applies to object being viewed
- Viewer Filter - applies to user logged in
- Attributes
- Normalize attribute names to match source attributes. The new Display Names can remain as they are.
- When using the dropdown list to select attributes, you may select more than one attributes. It will be considered with a FirstNotNull() function in the order the attributes were selected.
- If consideration of data from multiple silos are necessary:
- Clear the Silo Selection
- Utilize a functions such as FirstNotNull(AD.title, HV.title)
- Special Properties
- Name
- Usually Display Name
- Will be displayed in Thumbnails
- Title
- Usually Job Title
- Will be displayed in Thumbnails
- Email
- Usually email. UPN may be valid.
- Access Panel will use this attribute for sending notifications.
- Name
- Reference Attributes
- No need to create reverse references.
- Bi-directional attributes are created automatically.
- Grid Sections
- Update any Grid sections to use the new normalized names that were set on attributes.
- HTML Templates
- Either copy from a v6 version or create a blank Projected Silo.
- Copy and past HTML template and HTML Row template
- Decorators
- Any links to Service Panel forms can be updated to call the form from the attributes in Projected Silos
- Caveat - only a pencil icon can be used
- Audience rules on the form will apply
- If a different icon is necessary, or if additional logic is to be applied to audiences, the URL can still be manually configured in a decorator.
- isAccoutType
- Utilized by Access Panel. Refers to user/person object types.
- isResourceType
- Utilized by Access Panel. Refers to group object types.
- Job Attributes
- Used for sorting and attestation
- Job Title, Department, EmployeeType
- Select only the lowest of nested.
- Only subSub...
- Only DepartmentId or DepartmentDescription
- Risks
- Used in Attestation
- EmployeeStatus - if A, then 0, otherwise 2.
Comments
0 comments
Article is closed for comments.