Default Login
Signs members in against WordPress itself, with no Ultimate Member form driving the fields.
Use it when your site does not run Ultimate Member, or when you want a plain sign-in rather than your community form.
Before you start
Section titled “Before you start”| Plugin | None. WordPress core |
| Endpoint group | Default Authentication |
| Plan | Every plan |
Not the Authentication group. That one is Ultimate Member’s, and enabling it for this feature fails exactly like a wrong password. This is the single most common mistake with this screen.
Add it to your app
Section titled “Add it to your app”- Drag Default Login onto a navigation bar or the side drawer.
- Set after login.
- Configure social providers and Turnstile if you want them.
Settings
Section titled “Settings”| Setting | What it does | Default |
|---|---|---|
| Show remember me | A “remember me” checkbox | On |
| Show register button | A link through to registration | On |
| Allowed roles | Which WordPress roles may sign in | All |
| Social providers | Which providers to offer | None |
| After login | Where members land | Stay where they are |
| Appearance | Screen background, form wrapper, button styling | Inherits app tokens |
Allowed roles
Section titled “Allowed roles”An allow-list. A member whose role is not listed is refused with correct credentials.
Useful for an app meant only for paying members. Also an easy way to lock yourself out of testing, so check it before assuming a password is wrong.
Turnstile
Section titled “Turnstile”Cloudflare Turnstile needs both halves of the key pair, set on your site under Memberside → API Keys:
- The site key is compiled into your app.
- The secret key stays on your site and verifies the challenge.
The secret never ships in a build. With only the site key set, the challenge renders and every verification fails.
What your members see
Section titled “What your members see”Username and password fields with your app’s own field and button styling, plus whatever provider buttons and challenge you configured.
Validation errors are per-field rather than one message at the top.
The Default Login screen, with a social provider
record → src/assets/media/default-login.mp4
When it does not work
Section titled “When it does not work”| Symptom | Cause | Fix |
|---|---|---|
| Correct credentials refused | Authentication is on instead of Default Authentication | Enable the right group |
| One member refused, others fine | Their role is not in the allow-list | Add it, or clear the list |
| Turnstile always fails | Only the site key is set | Set the secret key on your site |
| Social sign-in works in preview, fails on the phone | The signing SHA-1 is not registered | Android signing |
| Signs in, screens still look signed out | The Users group is off | Enable it |