You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current implementation of the authentication providers, the QuickBooks provider is missing the sandbox settings. This is causing issues when trying to authenticate with QuickBooks in a development or testing environment.
Expected behavior
The QuickBooks provider should have a condition to check if the application is in development mode and if so, switch to the sandbox endpoint for user information.
Actual behavior
The QuickBooks provider always uses the production endpoint for user information, regardless of the application environment.
The text was updated successfully, but these errors were encountered:
This isn't exactly what was requested but I was able to use the QuickBooks provider in sandbox by overriding the UserInformationEndpoint property. I have it hardcoded in this example but you could read it from appsettings.json and override it in appsettings.development.json
Thank you for getting back. It's good for me to update the UserInformationEndpoint property for a sandbox. However, in other providers that have sandbox/production or similar setups, we can simply set the environment instead of providing the specific endpoints.
Describe the bug
In the current implementation of the authentication providers, the QuickBooks provider is missing the sandbox settings. This is causing issues when trying to authenticate with QuickBooks in a development or testing environment.
Expected behavior
The QuickBooks provider should have a condition to check if the application is in development mode and if so, switch to the sandbox endpoint for user information.
Actual behavior
The QuickBooks provider always uses the production endpoint for user information, regardless of the application environment.
The text was updated successfully, but these errors were encountered: