azure-ad-graph-api

Microsoft graph Unable to read JSON request payload

僤鯓⒐⒋嵵緔 提交于 2021-01-28 01:53:00
问题 I'm trying to create subscriptions with microsoft graph in php, however I am unable to see what is going wrong at this point. The code is breaking at the following: protected $http_subscribe = "https://graph.microsoft.com/v1.0/subscriptions"; public function getSubscriptions() { if(empty($this->token)) { dd('no token supplied'); //some debugging } $date = $this->endTimeDate->format('Y-m-d'); //This is Carbon date $time = $this->endTimeDate->format('H:i:s.u'); $response = $this->client-

Azure AD GraphServiceClient can't set AdditionalData against User

眉间皱痕 提交于 2021-01-27 12:42:07
问题 I am using the GraphServiceClient with .Net Core 2. I am trying to add AdditionalData to my Users using the following code var updated = new User() { AdditionalData = new Dictionary<string, object> { {"OtherEmail", otherEmail}, {"OtherRole", otherRole} }, }; await _graphClient.Users[user.Id].Request().UpdateAsync(updated); When this executes I get the following error Microsoft.Graph.ServiceException : Code: Request_BadRequest Message: One or more property values specified are invalid. Does

MSAL - Problem acquiring token with IntegratedWindowsAuth

匆匆过客 提交于 2021-01-05 09:49:24
问题 I am using MSAL to acquire token from an auth app in Azure using integrated windows authentication. The code is: var tenant = $"https://login.microsoftonline.com/<myTenantId>"; var clientId = "<myClientId>"; var scopes = new string[] { "https://graph.microsoft.com/.default" }; var publicApplication = PublicClientApplicationBuilder.Create(clientId).WithAuthority(tenant).Build(); var token = await publicApplication.AcquireTokenByIntegratedWindowsAuth(scopes).ExecuteAsync(); This throws the

Validating a Microsoft Graph JWT Token

十年热恋 提交于 2021-01-01 13:34:29
问题 I'm by no means an expert on MSAL/JWT/Graph authentication, but I'm hoping someone can explain this issue more clearly to me, or help me understand if there's a workaround or better approach. Essentially, there are certain scenarios where I might end up with a Microsoft Graph JWT token. Two examples I can think of easily are using the Microsoft Graph Toolkit or using Tabs SSO in Microsoft Teams. In both cases, I can get relevant identity information for the user from the JWT token I would

Validating a Microsoft Graph JWT Token

被刻印的时光 ゝ 提交于 2021-01-01 13:30:25
问题 I'm by no means an expert on MSAL/JWT/Graph authentication, but I'm hoping someone can explain this issue more clearly to me, or help me understand if there's a workaround or better approach. Essentially, there are certain scenarios where I might end up with a Microsoft Graph JWT token. Two examples I can think of easily are using the Microsoft Graph Toolkit or using Tabs SSO in Microsoft Teams. In both cases, I can get relevant identity information for the user from the JWT token I would

Validating a Microsoft Graph JWT Token

爷,独闯天下 提交于 2021-01-01 13:29:54
问题 I'm by no means an expert on MSAL/JWT/Graph authentication, but I'm hoping someone can explain this issue more clearly to me, or help me understand if there's a workaround or better approach. Essentially, there are certain scenarios where I might end up with a Microsoft Graph JWT token. Two examples I can think of easily are using the Microsoft Graph Toolkit or using Tabs SSO in Microsoft Teams. In both cases, I can get relevant identity information for the user from the JWT token I would

InefficientFilter error on Microsoft Graph requests which were previously working

穿精又带淫゛_ 提交于 2020-12-29 14:14:56
问题 Making the following request to the MS Graph to retrieve flagged messages ordered by due date: https://graph.microsoft.com/beta/me/messages?$filter=flag/flagStatus%20eq%20%27flagged%27&$orderby=flag/dueDateTime/dateTime%20desc&$top=100 would previously succeed and give back the expected results. Recently some users have been getting the following response: { "error": { "code": "InefficientFilter", "message": "The restriction or sort order is too complex for this operation.", "innerError": {

InefficientFilter error on Microsoft Graph requests which were previously working

≡放荡痞女 提交于 2020-12-29 14:13:55
问题 Making the following request to the MS Graph to retrieve flagged messages ordered by due date: https://graph.microsoft.com/beta/me/messages?$filter=flag/flagStatus%20eq%20%27flagged%27&$orderby=flag/dueDateTime/dateTime%20desc&$top=100 would previously succeed and give back the expected results. Recently some users have been getting the following response: { "error": { "code": "InefficientFilter", "message": "The restriction or sort order is too complex for this operation.", "innerError": {