Feature Overview (aka. Goal Summary)  

The current user registration flow for our cloud services customers is quite broken. Customers visiting the hybrid cloud console are prompted to create a simple (thin profile) user account which requires the customers to provide only 5 fields. When they visit OCM, they are prompted to provide additional details as OCM requires that customers have a full profile today. Subsequently, when they visit a section of OCM that pertains to OSD/ROSA (managed services), they additionally need to review and accept the appendix-4 terms. This is a step-wise process that presents multiple disruptions to the customer flow.

This issued has been discussed with the CIAM, HCC, and UXD teams and we have a new proposed login/registration flow.

https://docs.google.com/presentation/d/1kX-kCWjZaCoinKZKnhk8Ep9xgTyiVpd23Ela7A6chKg/

Goals (aka. expected user outcomes)

Simplify the login/registration flow for OCM customers, regardless of their entrypoint and destination. Customers could be visiting OCM from HCC, a RH marketing page, or from AWS and still have a streamlined login/registration flow (captured in the deck).

Requirements (aka. Acceptance Criteria):

• OCM landing pages (except those related to managed services) should only require the thin profile
• OCM pages related to managed services should require the full profile and the appendix-4 terms. These pages should present the user with the combined long form for user registration/profile.
• OCM should stop creating the OCP eval subscription for new OCM customers to trigger the EBS account ID generation
• * Need to confirm if not having an EBS account ID breaks anything in the OCM flow

Use Cases (Optional):

See deck: https://docs.google.com/presentation/d/1kX-kCWjZaCoinKZKnhk8Ep9xgTyiVpd23Ela7A6chKg/
 

Questions to Answer (Optional):

• Frederick needs to confirm if there is an export control dependency to have a full profile. The current understanding is that we do not need the full profile to be able to give customers access to the OCP installer and pull secrets.

• OCM engineering team to confirm if having users without EBS account ID will result in any issues.

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

Interoperability Considerations

Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.