Google client ID
Enable Google Sign-In. Requires both Google client ID and Google client secret. To create client id and secret, read Create authorization credentials.
Note When you configure your project at google.com, the Authorized Redirect URI should be set as https://www.company.com/basepath/login/check-google, replace "https://www.company.com/basepath" by the real URL of your project.
Google client secret
Enable Google Sign-In. Requires both Google client ID and Google client secret. To create client id and secret, read Create authorization credentials.
Facebook app ID
Enable Facebook Login. Requires both Facebook app ID and Facebook app secret. To implement Facebook Login, you need a Facebook App ID before you start, read Create an App with Meta.
Note When you configure your app at App Dashboard, the Redirect URI should be set as https://www.company.com/basepath/login/check-facebook, replace "https://www.company.com/basepath" by the real URL of your project.
Facebook app secret
Enable Facebook Login. Requires both Facebook app id and Facebook app secret. To implement Facebook Login, you need a Facebook App ID before you start, read Create an App with Meta.
Microsoft app ID
Enable Microsoft Entra ID Single Sign-On. Requires both Microsoft app ID and Microsoft app secret value. To implement Azure Single Sign-On, you need a Microsoft app ID before you start, see Register an application.
Note When you configure your app at Azure portal, the Redirect URI should be set as https://www.company.com/basepath/login/check-microsoft, replace "https://www.company.com/basepath" by the real URL of your project.
Microsoft app secret value
Enable Microsoft Entra ID Single Sign-On. Requires both Azure app id and Microsoft app secret value. You need to add a new client secret to your Azure app at Azure portal and then copy the client secret value here.
Notes
  1. After creating the client secret at Azure portal, make sure you copy the client secret value immediately. Client secret values cannot be viewed, except for immediately after creation. Be sure to save the secret when created before leaving the page.
  2. Copy the client secret Value, NOT the Secret ID.
Use OAuth2
Use other OAuth2 providers for authentication. PHPMaker uses [HWIOAuthBundle](https://github.com/hwi/HWIOAuthBundle) to add support for authenticating users via OAuth1.0a or OAuth2 in Symfony.This bundle contains support for 58 different providers, if you don't use Google/Facebook/Microsoft but use other providers, you can enable this setting so the required code (e.g. add the bundle "hwi/oauth-bundle" in composer.json, enable the bundle in Symfony, add routing, etc.) will be generated. However, you need to set up the configuration for other providers yourself: 1. Add your configuration for the provider to `Config('HWI_OAUTH.resource_owners')`, see [Configuring resource owners](https://github.com/hwi/HWIOAuthBundle/blob/master/docs/2-configuring_resource_owners.md) for details. 1. Add the login checking route for the provider under `Config('SECURITY.firewall.main.oauth.resource_owner')`. 1. Setup the `color` (for displaying the login link in the login page) and the `identifyingAttribute` (for finding the user in the user table) for the provider under `Config('EXTERNAL_LOGIN_PROVIDERS')`. You can enable one of the supported provider (e.g. Google), generate scripts, and see the generated _src/config.php_ as example.