Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pulled EmailProviderConfig credentials from last enabled for site rather than SiteConfiguration. #122

Conversation

ztraboo
Copy link

@ztraboo ztraboo commented Oct 24, 2021

Here were two decisions in moving this Third-party Auth credential information from SiteConfiguration:

  • Third-Party Auth Provider backend should contain all relevant information is it's the one who uses the information.
  • Allows for multiple backend from BigCommerceCustomer provider to have it stored on the ProviderConfiguration rather than SiteConfiguration (e.g. default site, another subsite).

…her than SiteConfiguration.

Here were two decisions in moving this Third-party Auth credential information from SiteConfiguration:
- Third-Party Auth Provider backend should contain all relevant information is it's the one who uses the information.
- Allows for multiple backend from BigCommerceCustomer provider to have it stored on the ProviderConfiguration rather than SiteConfiguration (e.g. default site, another subsite).
@ztraboo ztraboo force-pushed the feature.juniper/ztraboo/jyIZBpRtp0C2umLkLXbGjWQAGapM/Customer-Authentication-BigCommerce branch from 751ee92 to 3efa294 Compare October 24, 2021 15:03
@ztraboo ztraboo merged commit 0f2e510 into develop/juniper.master Oct 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant