@W-17458080 - Use env vars to configure redirect and callback uris for social/passwordless login & reset password

[yunakim714]

Description

Customers may want to change the application behavior for social and passwordless login without having to redeploy their bundle. Environment variables will make this easily configurable.

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

• Customers can change the callback & redirect uri's for social login, passwordless login, and password reset with the following environment variables:
  • SOCIAL_LOGIN_REDIRECT_URI
  • PASSWORDLESS_LOGIN_CALLBACK_URI
  • PASSWORD_RESET_CALLBACK_URI

How to Test-Drive This PR

• Go to https://runtime-admin-staging.mobify-storefront.com/salesforce-internal/wasatch-mrt/reset-password-poc/environment-variables (make sure bundle 131 is deployed)

• Change the SOCIAL_LOGIN_REDIRECT_URI environment variable to a random path

• Go to https://wasatch-mrt-reset-password-poc.mrt-storefront-staging.com/

• Click on the Google login button

• Open Network in DevTools and verify that the redirect URI of the API request is equivalent to the env var value

• Then delete the env var

• Go back to the storefront and click Google again

• Verify that the redirect URI is now the default value, or /social-callback

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[yunakim714]

The current client ID in the config is a public client, do we want to change this back to false?