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
{{ message }}
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.
@protocolist thank you for sharing this with us. This particular issue will be addressed with the upcoming release. You can work around it by specifying a random value for the scopes parameter. Right now the plan is to have version 3.0.6 release by the end of next week at the latest.
@IsaiahWilliams Thanks for the update and workaround. If I specify a random value for the scopes parameter, I am still unable to continue and am met with the following:
New-PartnerAccessToken : No ClientId was specified.
At line:1 char:10
+ $token = New-PartnerAccessToken -Module ExchangeOnline -RefreshToken ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : CloseError: (:) [New-PartnerAccessToken], MsalClientException
+ FullyQualifiedErrorId : Microsoft.Store.PartnerCenter.PowerShell.Commands.NewPartnerAccessToken
@protocolist the required code changes have been made. This will be officially addressed in version 3.0.6 which is scheduled to be released by tomorrow
Steps to reproduce
The issue is similar to #254
Run the command to exchange a refresh token for an access token as per microsoft documentation here, after first getting the refresh token:
$token = New-PartnerAccessToken -Module ExchangeOnline -RefreshToken $token.RefreshToken -Tenant $customerId
Expected behavior
An object with an Access Token is returned
Actual behavior
Powershell requests a scope
$token = New-PartnerAccessToken -Module ExchangeOnline -RefreshToken $token.RefreshToken -Tenant $customerId
cmdlet New-PartnerAccessToken at command pipeline position 1
Supply values for the following parameters:
(Type !? for Help.)
Scopes[0]:
Diagnostic logs
Environment
PartnerCenter 3.0.5
PSVersion 5.1.17763.771
The text was updated successfully, but these errors were encountered: