File tree 2 files changed +20
-13
lines changed
2 files changed +20
-13
lines changed Original file line number Diff line number Diff line change @@ -19,6 +19,7 @@ Parse Server supports 3rd party authentication with
19
19
* vKontakte
20
20
* WeChat
21
21
* Weibo
22
+ * Microsoft Graph
22
23
23
24
Configuration options for these 3rd-party modules is done with the ` auth ` option passed to Parse Server:
24
25
@@ -293,6 +294,22 @@ Learn more about [PhantAuth](https://www.phantauth.net/).
293
294
}
294
295
```
295
296
297
+ ### Microsoft Graph ` authData `
298
+
299
+ ``` js
300
+ {
301
+ " microsoft" : {
302
+ " id" : " user's microsoft id (string)" , // required
303
+ " access_token" : " an authorized microsoft graph access token for the user" , // required
304
+ " mail" : " user's microsoft email (string)"
305
+ }
306
+ }
307
+ ```
308
+
309
+ Learn more about [ Microsoft Graph Auth Overview] ( https://docs.microsoft.com/en-us/graph/auth/?view=graph-rest-1.0 ) .
310
+
311
+ To [ get access on behalf of a user] ( https://docs.microsoft.com/en-us/graph/auth-v2-user?view=graph-rest-1.0 ) .
312
+
296
313
## Custom authentication
297
314
298
315
It is possible to leverage the OAuth support with any 3rd party authentication that you bring in.
@@ -317,3 +334,4 @@ For more information about custom auth please see the examples:
317
334
- [ Facebook OAuth] ( https://github.com/parse-community/parse-server/blob/master/src/Adapters/Auth/facebook.js )
318
335
- [ Twitter OAuth] ( https://github.com/parse-community/parse-server/blob/master/src/Adapters/Auth/twitter.js )
319
336
- [ Instagram OAuth] ( https://github.com/parse-community/parse-server/blob/master/src/Adapters/Auth/instagram.js )
337
+ - [ Microsoft Graph OAuth] ( https://github.com/parse-community/parse-server/blob/master/src/Adapters/Auth/microsoft.js )
You can’t perform that action at this time.
0 commit comments