Authentication provider<\/h2>\n
Aligned with the efforts of standardization across Microsoft Graph SDKs, the new authentication provider handles the fetching, caching, and refreshing of tokens automatically. This ensures all of your requests are always authenticated. The auth provider makes sure the token is always valid by tracking the expiration and automatically refreshing it in the background before it expires.<\/p>\n
https:\/\/gist.github.com\/isvargasmsft\/12795cf818f0c4a80746804ff44d25b1<\/p>\n
The authentication provider wraps around PHP League’s\u00a0OAuth 2.0 client<\/a>, hence, its name \u2013 `PhpLeagueAuthenticationProvider`.<\/p>\n The authentication provider supports the following flows:<\/p>\n It also supports OAuth 2.0 on-behalf-of flow<\/a> to request tokens on behalf of third-party applications.<\/p>\n The fluent pattern makes the request building experience more intuitive. Rather than passing raw URLs, this new version provides a fluent experience to enhance discoverability and efficiency, while reducing the time spent in reference docs.<\/p>\n https:\/\/gist.github.com\/isvargasmsft\/fb768299ac9e2121a359290c404c3e4e<\/p>\n A configurable built-in retry handler understands 429, 503 and 504 response status codes, reading the information in the `Retry-After` header and taking decisions accordingly. The handler reads the recommendation for throttling status codes in the `Retry-After` header and retries after the recommended time.<\/p>\n See an example<\/a>\u00a0on how to customize middleware.<\/p>\n Get started now with the Upgrade guide<\/a>, the README<\/a> and code samples<\/a>. We have written a detailed description of the breaking changes introduced by this new version. You can also find the packages for the beta endpoint here<\/a>.<\/p>\n\n
Fluent request builder pattern<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2022\/06\/Graph-PHP-SDK.png\")
<\/a><\/p>\nBuilt-in retry handler<\/span><\/h2>\n
Get started<\/h2>\n