microsoftgraph / microsoftgraph/msgraph-metadata

Beta: `ODataUnrecognizedPathException` for `/roleManagement/exchange/roleAssignments/{unifiedRoleAssignment-id}/directoryScope`

Open
#512 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ToTriage
Dominant language
XSLT
Stars
166
Forks
55
Avg merge
16h 12m
Merged PRs (30d)
14

Description

It seems that metadata for beta contains definitions for endpoints that are not present.

I have a role assignment for Exchange Online provider with a specific directory scope, but the client generated from metadata for beta endpoint throws Microsoft.OData.UriParser.ODataUnrecognizedPathException

{
    "error": {
        "code": "UnknownError",
        "message": "Microsoft.OData.UriParser.ODataUnrecognizedPathException: Resource not found for the segment 'directoryScope'.   at Microsoft.OData.UriParser.ODataPathParser.CreateDynamicPathSegment(ODataPathSegment previous, String identifier, String parenthesisExpression)   at Microsoft.OData.UriParser.ODataPathParser.CreateNextSegment(String text)   at Microsoft.OData.UriParser.ODataPathParser.ParsePath(ICollection`1 segments)   at Microsoft.OData.UriParser.ODataPathFactory.BindPath(ICollection`1 segments, ODataUriParserConfiguration configuration)   at Microsoft.OData.UriParser.ODataUriParser.Initialize()   at Microsoft.Exchange.Admin.OData.Core.Handlers.RequestHandler.DeriveEntityFromQueryString()   at Microsoft.Exchange.Admin.OData.Core.Handlers.RequestHandler..ctor(ODataContext dataContext, Func`2 shouldSkipExceptionHandlingDelegate)   at Microsoft.Exchange.Admin.Library.BetaHttpHandler.ProcessRequest(HttpContext context)",
        "innerError": {
            "date": "2023-11-23T13:38:28",
            "request-id": "c0ad0750-383d-4de0-bac5-17ad80d6c03c",
            "client-request-id": "4fa91ad7-121d-ede1-43c3-42437af6fe49"
        }
    }
}

Happening when client calls GET /roleManagement/exchange/roleAssignments/{unifiedRoleAssignment-id}/directoryScope

Similar for

GET /roleManagement/exchange/roleAssignments/{unifiedRoleAssignment-id}/principal
GET /roleManagement/exchange/transitiveRoleAssignments

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the beta metadata definitions with the reported Exchange role-management paths: directoryScope, principal, and transitiveRoleAssignments. Confirm whether these paths are advertised despite being unavailable, then verify that the metadata and the corresponding service behavior agree.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.