-
Notifications
You must be signed in to change notification settings - Fork 29
[WIP] Add Azure region to support regional ESTS-r #71
base: master
Are you sure you want to change the base?
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
src/New-MsalClientApplication.ps1
Outdated
[Parameter(Mandatory = $false, ParameterSetName = 'ConfidentialClientClaims', ValueFromPipelineByPropertyName = $true)] | ||
[Parameter(Mandatory = $false, ParameterSetName = 'ConfidentialClientAssertion', ValueFromPipelineByPropertyName = $true)] | ||
[Parameter(Mandatory = $false, ParameterSetName = 'ConfidentialClient-InputObject', ValueFromPipelineByPropertyName = $true)] | ||
[string] $AzureRegion = [Microsoft.Identity.Client.ConfidentialClientApplication]::AttemptRegionDiscovery |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be a parameter of type string? ESTS-R SHOULD most certainly not be enabled by default.
Note that for ESTS-R to work you need Certificate with SN/I, via the "sendX5C" param. Is this exposed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The parameter was of type string. Here i was simply setting it to the TryAutoDetect const that the library provides. The SendX5C parameter is exposed yes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need update to latest MSAL + other comments
Confidential clients should use regional ests-r