Enhance load-error event handling for ZuoraSimple Component
What does this MR do and why?
Improves load-error event handling for Zuora component
Resolves #362468 (closed)
Screenshots or screen recordings
Identity verification | Account validation |
---|---|
Successful load (as before) |
How to set up and validate locally
Identity verification
-
Ensure that you have a running CustomersDot installation locally and Zuora is set up to use
GL.com CC Validation_registration
hosted page with the correct callback to your local GDK instance -
Enable
arkose_labs_signup_challenge
feature. This feature is responsible for interfacing with Arkose Labs to assign arisk_band
for new users.$ rails console > Feature.enable(:arkose_labs_signup_challenge) > ApplicationSetting.first.update({ arkose_labs_public_api_key: '****', arkose_labs_private_api_key: '****', arkose_labs_namespace: 'client' })
Credentials are available in GitLab 1Password Engineering Vault
-
Set
require_admin_approval_after_user_signup
to false so user can sign in without needing admin approval$ rails console > ApplicationSetting.first.update(require_admin_approval_after_user_signup: false)
-
Enable feature flags for identity verification
$ rails console > Feature.enable(:identity_verification) > Feature.enable(:identity_verification_credit_card)
-
Sign up for a new account. After, you should be redirected to the Identity Verification page (
http://localhost:3000/users/identity_verification
) -
Update the user's (the same user you created previously) risk band data to have
'High'
value$ rails console > u = User.last > risk_band = u.custom_attributes.by_key('arkose_risk_band').first > risk_band.update(value: 'High')
-
Refresh the Identity Verification page
Account validation:
Follow these steps to setup and verify locally
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.