Goal: 

• As a developer I want the frontend actions to be connected to the backend operations, so I can complete the registration process from UI.

Acceptance Criteria:

• HMS-2667 - On page 1 the token creation is launched in background, and Next button is enabled when a success response happens.
• HMS-2593, HMS-2590 - On page 2 a polling is launched to check when the user as registered the domain from its IPA server, and Next button is enabled when a success response happens; furthermore when the user click "Test" button again, the polling start again; polling stop on timeout or when a success response is got.
• In page 3 when the Next button is clicked, the internal state is updated (not communicated to the backend yet).
  When back button is clicked, the current state is hold internally.
• In page 4 when the Finish button is clicked, the PATCH /domains/:domain_id is sent with the internal state to set title, description, and auto_join_enrollment properties; double-check when it is happening and if for the instant we wish.
• When cancel is clicked:
  • Page 2, if the domain has been registered, intent to DELETE /domains/:domain_id, else don't do anything.
  • Page 3, trigger DELETE /domains/:domain_id
  • Page 4, trigger DELETE /domains/:domain_id

Additional Information:

• See: HMS-1688 which add some communication with the api backend.
• Simulate network situation by shutting down the backend service locally.