Quantcast
Channel: Azure Active Directory forum
Viewing all articles
Browse latest Browse all 16000

Azure Information Protection Scanner deployment - error acquiring token 2

$
0
0

I read the previous question with same name.

To set the stage:  The service account has already been granted Log on locally right.

                          Azure Rights Management is activated

                          I am running Powershell as the service account that is synced to Azure AD

I am using this format: Set-AIPAuthentication -webAppId "<The ID of my Web app / API app>" -webAppKey" <The Key value generated by my Web app / API app>" -nativeAppId "<The ID of my Native app>"

I get the error acquiring token when using all 3 parameters: -webAppId -webAppKey -nativeAppId  

                         I am able to get the token if I run only 2 of the parameters, doesn't matter which 2

The login screens are different when using 3 parameters vs 2  - I have tried the token method same results can't generate the token

Unable to show screenshots until verified    3 parameters is a Microsoft at top of login vs Microsoft Azure Information Protection when only 2 parameters are used 

Is the Authorization token different if you successfully run the parameters individually vs all at the same time?

Each of these lines run successfully and acquire a token

Set-AIPAuthentication -webAppId "<The ID of my Web app / API app>"

Set-AIPAuthentication -webAppKey" <The Key value generated by my Web app / API app>"

Set-AIPAuthentication -nativeAppId "<The ID of my Native app>"

 


Viewing all articles
Browse latest Browse all 16000

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>