Item

References

Details

Short Description

Install Identity Panel – SaaS

Install Identity Panel - On Prem

Installlation of

• Identity Panel App on TBA
• PanelService on TBA

Description

What is being changed?

• Environment (e.g. Dev/QA/Prod): TBA

• App Service Host (uri or fqdn/ip/port): TBA

• Panel Service Host (fqdn/ip): TBA

Why is it being changed?*

(Add or delete as appropriate)

• Microsoft Identity Manager (MIM) is nearing the end of Microsoft Support

• App/Panel Services on version 7.x is a dependency for migrating from MIM to HyperSync on Identity Panel

How is it being changed?

• SIDM installation of App Service (web)
  (Delete one of the following)

  • Hosted: performed remotely by SIDM

  • On premises: performed on site by SIDM

• SIDM on site for local installations of Panel Service

Which Teams are involved?

• SIDM

• <ORG> teams: TBA

*Note: Identity Panel versions 5.x are unsupported by SoftwareIDM.  The risk of NOT upgrading is possibly greater than remaining on an unsupported platform

Justification

Business Justification (examples):

• <ORG> risk non-compliance by remaining on an unsupported Identity Management platform

• <ORG> risk non-compliance by remaining on unsupported Windows on-premises infrastructure

• An Identity Panel installation to the latest v7.x release is required to support the planned replacement of MIM Sync with HyperSync

Test Plan

 <TBA - Test Plan URI>

Refer to referenced Test Plan document

Implementation Plan

 <TBA - Implementation Plan URI>

Refer to referenced Implementation Plan document

Communication Plan

 <TBA - Communication Plan URI>

1.Advise <ORG> <Division> of change for review

2.<ORG> to advise relevant affected system owners as required

Post Verification Plan

 <TBA - Verification Plan URI>

Refer to referenced Verification Plan document

Rollback Plan

 <TBA - Rollback Plan URI>

Refer to referenced Rollback Plan document

Risk Analysis

Business: Risk to <ORG> of business disruption if change fails

Technical: e.g. Simple; Done before; Single team involved or. Complex; Not previously performed; Multiple teams involved.

Services: Risk to <ORG> of production service disruption if change fails

Risk Mitigation

Business: Rollback Plan prepared and tested.  Communication Plan in place.

Technical: Installation performed successfully in lower environments. SIDM engineering on hand to resolve any issues as they arise with the <ORG> teams.

Services: Post Verification process prepared and tested. Rollback Plan prepared and tested.  Communication Plan in place.

Impact analysis

Business: e.g. Removal of blocker for planned transition from MIM to HyperSync (dependent project)

Technical: e.g. Identity Panel installation previously performed successfully in NON-PROD will be able to be completed in PROD.

Services: e.g. 2-hour outage of Identity Synchronisation services will delay on-boarding and off-boarding but will not disrupt access for existing users

Consequence of No Change or decision to NOT implement*: e.g. Identity Management Operations remain on an unsupported platform and/or infrastructure (<ORG> may be non-compliant), and any planned transition to HyperSync cannot proceed.

*Note: the consequence of no change for sites on version 5.x or lower represents a significant risk to the <ORG> organization.

Risks include (but are not limited to) the following:

• Security risks in not adopting the latest App Service modern authentication patterns

• <ORG> may presently be non-compliant

• TBA