Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Cognitive Services docs state that "Cognitive Services User" role is required, but it is not. #12814

Closed
jongio opened this issue Jun 16, 2020 · 2 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Cognitive - Form Recognizer Cognitive - Text Analytics Cognitive Services
Milestone

Comments

@jongio
Copy link
Member

jongio commented Jun 16, 2020

Here: https://azuresdkdocs.blob.core.windows.net/$web/dotnet/Azure.AI.FormRecognizer/1.0.0-preview.3/api/index.html#create-formrecognizerclient-with-azure-active-directory-credential

We have:

You will also need to register a new AAD application and grant access to Form Recognizer by assigning the "Cognitive Services User" role to your service principal.

But I have found that this role is not required.

The API run successfully without any additional roles assigned.

azsdke2e

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jun 16, 2020
@maririos maririos added Client This issue points to a problem in the data-plane of the library. Cognitive Services FormRecognizer labels Jun 16, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jun 16, 2020
@maririos maririos added this to the [2020] July milestone Jun 16, 2020
@kinelski kinelski self-assigned this Jul 22, 2020
@kinelski
Copy link
Member

The Cognitive Services User role is now required. Strangely enough, it was not required before, but this recently changed (related: #13126). We're investigating if this was a service-side fix, but we're closing this issue since this is the desired behavior and no updates to the documentation are required.

This is the error message we get when trying to authenticate without the required role:

Azure.RequestFailedException
  HResult=0x80131500
  Message=Service request failed.
Status: 401 (PermissionDenied)

Content:
{"error":{"code":"PermissionDenied","message": "Principal does not have access to API/Operation."}}

@jongio
Copy link
Member Author

jongio commented Jul 27, 2020

Okay, Thanks for checking @kinelski

openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-net that referenced this issue Feb 26, 2021
Users/mayaggar/dataprotection (Azure#13168)

* New Readme Config File

* New Go Language Readme Config File

* New Azure AZ Readme Config File

* New Azure CLI Readme Config File

* New Typescript Language Readme Config File

* New Python Language Readme Config File

* New C# Language Readme Config File

* New AzureResourceSchema Readme Config File

* New Swagger Spec File

* New Swagger Example Spec File

* Microsoft.data protection (Azure#12814)

* moving changes from Private repo

* changes for autorest vqalidation err

* fix delete response

* fixing lint and model errors

* exposureControlledFeatures fixes

* prettier fixes

* fixing spell check issues

* adding backuptype in custom-words

* PolicyParameters related changes for Disk Backup

* fixing PR comments

* description changes

* changes for preview to stable folder

* changes for retention in monitoring

* changes for stable in readme

* fixing checklist gate issues

* changes for systemdata in dppresource

Co-authored-by: sumitmal <32121310+sumitmal@users.noreply.github.com>
Co-authored-by: Mayank Aggarwal <mayaggar@microsoft.com>
Co-authored-by: vityagi <vityagi@microsoft.com>

* MFA MUA DPP swagger changes (Azure#13081)

* MFA MUA DPP swagger changes

* Resolving PR comments

Co-authored-by: Madhumanti Dey <madhude@microsoft.com>

* Swagger changes for VaultGuardResource Object (Azure#13116)

* MFA MUA DPP swagger changes

* Resolving PR comments

* MFA MUA dpp swagger changes

* Fixed preetierCheck failures

* Fixed Avocado failures

* Fixed LintDiff warning

* resolved PR comments

* GO SDK fix

* Go SDK fix

* Go SDK fix

* preview related changes

* Go SDK fix

* resolved PR comments

Co-authored-by: Madhumanti Dey <madhude@microsoft.com>

* changes for preview DPP version

* fix for credscan SAS

Co-authored-by: sumitmal2711 <58544969+sumitmal2711@users.noreply.github.com>
Co-authored-by: sumitmal <32121310+sumitmal@users.noreply.github.com>
Co-authored-by: Mayank Aggarwal <mayaggar@microsoft.com>
Co-authored-by: vityagi <vityagi@microsoft.com>
Co-authored-by: deymadhumanti <58032062+deymadhumanti@users.noreply.github.com>
Co-authored-by: Madhumanti Dey <madhude@microsoft.com>
@github-actions github-actions bot locked and limited conversation to collaborators Mar 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Cognitive - Form Recognizer Cognitive - Text Analytics Cognitive Services
Projects
None yet
Development

No branches or pull requests

5 participants