SSO Cutover Planning

Before the cutover:

• Schedule a cutover time and date conducive to minimal production activity.
• Dedicate approximately 2 hours to establish the Ping Environment.
• Collaborate with partners for user cleanup, which includes verifying email addresses, ensuring appropriate user types for API activities, and providing the count of active users earmarked for migration to Fluent.

      4. Allocate 30 minutes for the partner to configure the External IDP.

On the cutover day:

• The partner stops any further user additions.
• They verify if the current user count matches the previously provided number; if not, they check for new users as outlined earlier.
• The partner notifies Fluent to begin user migration, with the duration dependent on the number of users.
• Fluent confirms the completion of the migration process.

Cutover (approximately 2 hours):

• Partner instructs all users to refrain from OMS front-end activities until the cutover is completed.
• They stop new orders from hitting Fluent.
• Partner notifies Fluent upon cessation of new orders.
• They clear the integration token cache and request Fluent to activate SSO.
• Fluent's team initiates SSO activation, typically taking around 15 minutes.
• Partner conducts comprehensive testing with all user types.
• A limited number of orders is allowed to flow into Fluent.
• Partner validates orders and communications.
• Partner confirms system stability and informs users that they can resume OMS activity.