Login with GitHub

GitHub sign-in suits developer-facing sites: documentation, plugin support, communities. It needs an OAuth app on your GitHub account or organisation.

1. Register the OAuth app

1. Open GitHub → Settings → Developer settings → OAuth Apps. For an organisation, use the organisation’s settings instead.
2. Click New OAuth App.
3. Fill in:

   • Application name: your site’s name, shown on GitHub’s consent screen.

   • Homepage URL: your site.

   • Authorization callback URL: copy it from FluentAuth → Settings → Social Login → GitHub. It is your login page with the provider named in the query string:

     https://example.com/wp-login.php?fs_auth=github&fs_type=confirm

     Make sure it is exact; GitHub compares it character for character.

4. Click Register application.
5. Copy the Client ID, then click Generate a new client secret and copy that too. The secret is shown once.

2. Connect it to FluentAuth

Paste the two values on the GitHub card under Settings → Social Login, or add them to wp-config.php:

define('FLUENT_AUTH_GITHUB_CLIENT_ID', 'Iv1.…');
define('FLUENT_AUTH_GITHUB_CLIENT_SECRET', '…');

Turn on Enable login with GitHub and save.

3. Test it

Open the login page in a private window and click Continue with GitHub. GitHub asks you to authorise the app once; after that, the button signs you straight in.

Email addresses

GitHub users can keep their email private. FluentAuth asks for the user:email scope and uses the account’s primary verified address, which works even when the address is hidden from the public profile. A GitHub account with no verified email cannot register.

Common errors