Sign in with Google for Mishka CMS. Each site switches it on and sets its own keys; no other setup is needed.
Install
# mix.exs
{:mishka_cms_auth_google, "~> 0.0.1"}Run mix deps.get and restart. The package registers itself with Mishka CMS through
mishka_installer; there is no config to add and no migration.
Set up
- Make the app at the Google Cloud console (APIs & Services → Credentials → OAuth client ID, type Web application).
- Authorized redirect URI:
https://<your-site>/api/auth/user/provider/callback - In Mishka CMS: Settings → Security → Sign-in methods → switch Google on. Paste the Client ID and Client secret into the fields that open under it, then Save.
The Google button now shows on the sign-in and registration pages.
What it does
- Google says whether the email is verified; only a verified one signs in. While the consent screen is in Testing, add your account under Test users.
- Links to an existing confirmed account with the same email, and claims one nobody confirmed.
- Makes a new account only while the site allows it, and never makes a master.
- Asks for the authenticator code when the account has two-step sign-in.
- Uses PKCE (S256) on top of the state check.
- Keeps none of Google's tokens.
License
Apache-2.0