Added CustomSSOCredentialsProvider to retain higher-level ClientConfiguration #3103
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
The existing
SSOCredentialsProvider
class was overwriting the higher-levelClientConfiguration
settings, which is leading to issue while authenticating through SSO.Added a new custom provider class calledCustomSSOCredentialsProvider
that inherits fromSSOCredentialsProvider
and allows the use of a customClientConfiguration
.In the
Reload()
method ofCustomSSOCredentialsProvider
, a newClientConfiguration
object is created using the providedm_clientConfig
member variable, and thescheme
andregion
properties are set before passing it to theSSOCredentialsClient
constructor.This will ensure that the higher-level
ClientConfiguration
is retained, and theSSOCredentialsClient
is created with the correct configuration.Check all that applies:
Check which platforms you have built SDK on to verify the correctness of this PR.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.