Skip to content

graphapi cleanFilter failure leads to lsc stop #1

@davidcoutadeur

Description

@davidcoutadeur

Graph API is very poor for filters:
https://docs.microsoft.com/fr-fr/graph/query-parameters#filter-parameter

Note: The following $filter operators are not supported for Azure AD resources: ne, gt, ge, lt, le, and not. The contains string operator is currently not supported on any Microsoft Graph resources.

This is very uncomfortable.

For example, I can't exclude these type of entries from the synchronization:

Feb 24 15:55:50 - ERROR - Error while synchronizing ID {mail=A.N'DOME@domain.com}: org.lsc.exception.LscServiceException: {
  "error": {
    "code": "BadRequest",
    "message": "Invalid filter clause",
    "innerError": {
      "request-id": "0e8f5835-a894-48e5-99bc-2327bf5205be",
      "date": "2020-02-24T14:55:50"
    }
  }
}

The problem is certainly the quote, but it would be nice to have the LSC going on after such failures.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions