Adjustment for new CIAM partition #564
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rayluo
force-pushed
the
ciam-in-new-partition
branch
3 times, most recently
from
c3a4874 to
592c88c
Compare
rayluo
force-pushed
the
ciam-in-new-partition
branch
from
592c88c to
49090cb
Compare
This was referenced Dec 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Our lab switched to a new CIAM test tenant.
The two lab API were also updated:
appIdfield from the response of the first API above. This way, in the future when/if the lab switch to a different client_id, your existing test automation will not break.There is one change needed in the Confidential Client's test case. No more hardcoded scope. The scope returned from lab API 2 will work out of the box.