New named credentials are powerful, but so damn painful :D And as always, Salesforce creates new features without fully supporting old functionality. In the case of named credentials, it's storing the password and username named credentials :)
No. The auth. provider is coded to use metadata in the background. If you need to update values from your code, I recommend storing that information in a custom setting outside the named credential storage.
New named credentials are powerful, but so damn painful :D And as always, Salesforce creates new features without fully supporting old functionality.
In the case of named credentials, it's storing the password and username named credentials :)
Are you setting the newly generated Callback Url from Auth Provider as the redirect URL in QB setup.
Yes that is correct
great job
Can we use custom setting instead of metadata?
No. The auth. provider is coded to use metadata in the background. If you need to update values from your code, I recommend storing that information in a custom setting outside the named credential storage.
Why didn't you use Open ID Connect for this?
You may be able to use Open ID Connect