Gatey – Login & SSO with Amazon Cognito

1. 
2. 
3. 
4. 
5. 
6. 
7. 
8. 

What is Gatey?

Gatey is a server-free WordPress plugin that adds Amazon Cognito login and SSO in minutes. Drop in its Authenticator block, shortcode or CSS class—no coding required.

Does Gatey store any user data or client secret?

No. Gatey never stores your Cognito client secrets or your users’ personal data on the WordPress server. All authentication happens directly in the browser against your own Cognito User Pool. The plug-in only keeps non-sensitive settings (e.g., User Pool ID) in WordPress and does not proxy, log, or persist any JWT tokens or profile details.

Is my data shared with any third party?

Gatey never shares your personal data or WordPress site data with any third party. Authentication flows run directly between your site and your AWS Cognito user pool. If you enable premium features, subscription management is handled securely via Stripe using hosted forms and client‑side JavaScript. No payment data is stored or processed by Gatey.

Will it still work after a static export?

Yes. Because all authentication runs in the browser, Gatey talks straight to Amazon Cognito and keeps working even when WordPress is served as static files (Netlify, S3, CloudFront, etc.).

Do I need AWS or Cognito knowledge to use it?

Only the basics. You’ll create a Cognito User Pool and App Client in the AWS console—that’s it. Gatey then takes over all front-end work — sign-in, sign-up, MFA, profile fields—through a visual block or shortcode, no coding required.

How long does setup take?

Usually less than five minutes: install, drop the block, paste your User Pool ID, App Client ID, and region.

Can I show or hide content based on the logged‑in user?

Yes. You can use shortcodes or CSS variables like –gatey-account-group-admin or –gatey-account-attribute-email to control visibility.

Is Gatey compatible with my theme?

Yes. Gatey uses standard Gutenberg blocks and shortcodes, so it works with any WordPress theme or builder (Elementor, Divi, etc.).

Do I need to register or subscribe to use Gatey?

No. Gatey works fully offline out of the box and requires no registration or subscription to function. You can configure your AWS Cognito user pool directly inside WordPress and use login, registration, MFA, and profile features without ever connecting to wpsuite.io. Premium features are entirely optional and only become available after connecting your site using secure client‑side JavaScript.

What’s the difference between plans?

Free includes all core blocks, social login (Facebook, Google, Amazon, Apple), but frontend customizations are hidden. Basic shows custom blocks on live pages. Professional unlocks custom SAML/OIDC providers, JWT/IAM‑secured APIs, and advanced Gatey control.

Where are the subscription-based configuration files stored, and how often are they refreshed?

All Pro settings you create in the Gatey Settings—API Settings, custom Form Fields—are saved server-side and, whenever you hit Save, an encrypted copy is written to your site’s wp-content/uploads/ folder.
The small licence file needed to decrypt that config are also stored in uploads. A licence is valid for one month, so the plugin automatically downloads a fresh file every seven days while your subscription is active.
If you run a static export, you’ll still need that weekly refresh (a short tutorial covers this topic), but a normal WordPress install handles it for you automatically.

Can I cancel or upgrade later?

Yes, at any time. The plugin will still work in Free mode, and your site’s blocks won’t break — only premium features will deactivate.

Hide FAQ

2.1.5

• Fixed a race condition during logout in the Authenticator block.
• Prevented premature redirect to the sign-in page before logout and Cognito token revocation completed.

2.1.4

• Improved the robustness of script loading and dependency ordering for shared functions, blocks, and related assets.
• Added defer loading where possible so scripts no longer block page rendering unnecessarily.

2.1.3

• Admin: Added a new “Hide Sign Up” setting in the admin UI to control whether the sign-up option is shown in login and sign-up forms.
• Admin: Added passwordless configuration options to the admin UI, including hidden authentication methods, preferred authentication method, and passkey registration prompt settings.
• UX: Makes key sign-in experience settings configurable directly from the plugin admin interface.

2.1.2

• Stability: Improved plugin bootstrap order so Gatey can no longer initialize before the shared WP Suite hub when multiple WP Suite plugins load together.
• Internal: Adjusted hub-loader sequencing and hardened global WpSuite namespace initialization to prevent race conditions during startup.
• Compatibility: Helps ensure more reliable interoperability with other WP Suite plugins that depend on the shared hub lifecycle.

2.1.1

• Improvement: updated the shortcode column rendering/behavior.

2.1.0

• Moved reCAPTCHA handling and script loading to the shared hub-for-wpsuiteio package.
• Added admin-configurable debug logging for monitoring plugin PHP execution when needed. Requires both WP_DEBUG and WP_DEBUG_LOG to be enabled.
• Fixed a redirection issue.
• Simplified attribute handling across all block rendering flows.
• Renamed the Redux store from wpsuite/gatey to smartcloud/gatey to better align with the naming convention used across other plugins.

2.0.15

Fix: Improved WebCrypto polyfill initialization so Gatey loads reliably even in insecure (non-HTTPS) environments.
Update: Refreshed the bundled Authenticator foundation to support upcoming authentication enhancements (including passwordless login).

2.0.14

• Fix: Gutenberg block registration now references the exact apiVersion from block.json, preventing asset mismatches.
• Fix: reCAPTCHA UI correctly hides itself, eliminating stray placeholders.

2.0.13

• Admin menu update: Gatey admin pages are now grouped under the unified SmartCloud top-level menu in WP Admin.
• Naming cleanup: standardized internal prefixes across PHP, JavaScript, and rendered HTML (classes, IDs, data attributes) using a smartcloud-gatey namespace to avoid collisions.
• Internal refactor only — no functional changes and no impact on existing configurations or frontend behavior.

2.0.12

• Change: removed the Authenticator block’s Custom CSS field to align with WordPress.org recommendations. You can still style the block using a custom CSS class and your theme/site styles.
• Cleanup: standardized PHP variable naming in render templates using the wpsuite_gatey_ prefix.

2.0.11

• Fix: improved Authenticator frontend rendering. Gutenberg layout classes are now applied to the correct wrapper element, so editor layout settings (alignment/width, etc.) reliably carry over to the frontend.

2.0.10

• Improvement: standardized chunk naming in gatey-blocks so the dynamically imported custom block parser now has a stable filename (custom-block-parser.js).
• Compatibility: enables static exports by allowing you to include a fixed URL for the chunk (e.g. [SITE_URL]/wp-content/plugins/gatey/gatey-blocks/dist/custom-block-parser.js) so all required chunks are available on the static site.

2.0.9

• Performance: externalized Mantine CSS to further reduce the plugin payload.
• Fix: corrected editor asset loading so admin/editor assets are no longer loaded unnecessarily in the Gutenberg editor.
• Cleanup: removed Amplify reconfiguration from gatey-admin (not needed).

2.0.8

• Fix: corrected the admin Mantine asset URL inside the plugin so Mantine loads properly.

2.0.7

• Fix: corrected hub-loader.php to ensure the shared SmartCloud admin menu loads reliably.

2.0.6

• Performance: corrected package entry points so the correct builds are loaded, significantly reducing shipped JS size.
• Performance: externalized the admin UI Mantine dependency (similar to Amplify), further reducing overall plugin size.
• Stability: improved plugin bootstrapping by switching from jQuery ready to DOMContentLoaded and inlining observer logic, making loading more reliable across frontend, Gutenberg and Elementor.

2.0.5

Fix: sanitize resolved configuration to AuthenticatorConfig keys only (prevents unknown keys leaking from getConfig() or site settings).

2.0.4

Authenticator: simplified backend config loading by replacing gatey.cognito.get with a plain site-key based fetch (used by the Gutenberg editor). The Cognito wrapper was unnecessary for this request.

2.0.3

Updated the Authenticator block: removed Amplify reconfiguration both on the frontend and in the admin, since the correct Amplify configuration is now provided centrally.

2.0.2

Replaced the reCAPTCHA hook with an in-house implementation so it can be used outside React components too (e.g. in plain JS/TS contexts).

2.0.1

Improved shared admin menu ownership detection: Fixed a case where the common SmartCloud admin menu could fail to load if the previously “active” plugin no longer existed under wp-content/plugins (e.g., the folder was renamed). The decision logic now also validates the filesystem.
reCAPTCHA provider update: Switched from the custom reCAPTCHA implementation to react-google-recaptcha-v3.

2.0.0

BREAKING: Introduced a unified WP Suite global registry and event-based initialization.

• New global namespace: use globalThis.WpSuite as the single entry point.
• New plugin registry: Gatey is now exposed under globalThis.WpSuite.plugins.gatey.
• New lifecycle events:
  • wpsuite:gatey:ready — fired when Gatey is fully initialized and the store is ready.
  • wpsuite:gatey:error — fired if initialization fails.
• Improved interoperability: dependent WP Suite plugins can reliably detect readiness without relying on script order.
• Internal refactor: Gatey runtime helpers now resolve state through the WP Suite plugin registry.

1.10.2

• Fixed a rendering issue in the Authenticator block
• Custom blocks are now visible again with an active subscription
• Custom blocks are also available in the Gutenberg editor when using the “PAID” preview mode

1.10.1

• Minor refinements and fixes in the WPSuite.io / Connect your Site admin menu
• Small internal improvements

1.10.0

• Refactored the admin codebase behind the WPSuite.io / Connect your Site menu
• Improved site connection and license management internals
• Prepared the foundation for upcoming WPSuite plugin integrations

1.9.2

• Pro features are now enabled again in the admin interface once a site is registered and connected to wpsuite.io
• Frontend behavior remains unchanged: Pro features are applied only with an active subscription or trial

1.9.1

• Minor fixes and refinements in the signIn and signOut hooks
• Improved reliability of authentication-related state handling
• Small internal cleanups

1.9.0

• Refined and reorganized internal dependencies for better performance and maintainability
• Fixed several TypeScript and linting issues across the codebase
• Significantly reduced JavaScript bundle sizes, especially on the frontend
• General internal cleanup and stability improvements

1.8.3

Fixed broken styling and attributes in multiple Gutenberg blocks.
The previous release escaped get_block_wrapper_attributes() incorrectly, which
prevented proper rendering of class names, inline styles, and data attributes.

1.8.2

Re-enabled the Hub for WPSuite.io functionality directly inside Gatey.
This component reconnects your WordPress instance with wpsuite.io for subscription and licence management — previously released as a separate plugin, but re-integrated here following WordPress.org review guidelines.
Also improved wp-login synchronization: changing an email address in Cognito no longer prevents successful WordPress login when the WP-login integration is enabled.
text

1.8.1

Removed an unnecessary debug log entry from the authentication flow to keep browser and server logs clean.

1.8.0

• New integration with the Hub for WPSuite.io plugin: licence validation and site connection have been moved into a shared component.
• Gatey’s admin pages (Settings and Patterns) now appear under the central WPSuite.io menu in wp-admin, alongside other WPSuite plugins.
• Minor UI refinements and code clean-up to support the new menu structure.

1.7.3

Removed the outdated BASIC plan and updated the pricing table to reflect the new WP Suite model (Free + Pro across all plugins).
Dependencies have been refreshed in the React/Node.js subprojects.

1.7.2

Fixed an Account Attribute scoping bug: when multiple blocks displayed the same attribute on a page (e.g., first name in the header and on the profile page), updating the data no longer applies the first block’s prefix/postfix to all others. Each instance now retains its own settings.

1.7.1

• General tab tidy-up — settings are now grouped in a clearer order.
• New switch: Hide “Powered by Gatey” text (enabled by default, so the link stays hidden unless you turn it off).

1.7.0

Social-login overhaul
– Google, Facebook, Apple, and Amazon sign-in buttons are now available on the free plan.
– On PRO you can display any number of custom OIDC / SAML identity-provider buttons on the Sign-In and Sign-Up screens.

1.6.4

Fixed the Account Attribute block: after a user updates the underlying data, your configured prefix and postfix are now retained instead of being replaced by the raw attribute value.

1.6.3

The Account Attribute block now supports link, prefix, and postfix attributes (prefix/postfix also available in the Elementor widget), letting you add links and extra text right in Gutenberg. The plugin also rewrites logout_url in WordPress integration mode, not just login_url.

1.6.2

Removed the “Powered by Gatey” footer from the free version’s Sign-In and Sign-Up screens; all plans now show a clean, unbranded interface.

1.6.1

Help docs updated: added a concise note explaining the Custom provider name field.

1.6.0

Bring your own IdP: Gatey now works with any identity provider configured in Amazon Cognito—SAML or OIDC—alongside the built-in Facebook, Google, Amazon, and Apple options. Just add the provider in Cognito and it appears automatically in the Authenticator settings.

1.5.1

• Account Attribute block – now fully inherits typography from the parent page/template; no more manual font overrides.
• Admin site selector – added a filter that lets you search your site list by name or primary domain, ideal for agencies with many projects.

1.5.0

• New Elementor widgets
  • Gatey Authenticator – drag-and-drop the full authenticator without touching shortcodes; every pattern attribute (screen, variation, language, etc.) is editable via native Elementor controls.
  • Gatey Account Attribute – display any Cognito user attribute with Elementor styling and attribute pickers, no shortcode required.

1.4.5

The Authenticator and Account Attribute blocks now default to font-family: inherit, so they automatically follow any typography set by your theme or the Gutenberg editor.

1.4.4

Form Field blocks now honour Gutenberg alignment controls: set Dimensions › Width when the field sits in a Row, or Dimensions › Height when it’s inside a Stack, giving you finer layout control.

1.4.3

Fixed the “Paid” preview inside the Gutenberg editor when you’re running the free plan: the Authenticator block now stays visible and reflects your current styling instead of disappearing.

1.4.2

Document Overview clarity: each Form Field block now shows its target attribute in the Gutenberg Outline, so you can see at a glance which field is which.
One-click field generator: in the Custom Block → Settings → Block tab (used for Sign Up and Edit Account screens) you’ll find an “Add Missing Form Fields” button. It auto-inserts every field required by your current loginMechanisms and signUpAttributes settings—no more dropping “Form Field” blocks one-by-one.

1.4.1

Added a Custom CSS field to the Authenticator block: style any element inside the widget without touching theme files.

1.4.0

Live form-builder in Gutenberg – Sign-Up and Edit-Account screens are now edited directly in the block editor. Drag fields, Rows, Stacks and any other core layout blocks, and see your changes instantly.
Field order, labels, visibility and full page layout are all controlled in one place—no more sidebar lists.

1.3.6

The reCAPTCHA provider is now enqueued inside the Gutenberg editor whenever a Site Key is set, so the Authenticator block renders correctly during editing.

1.3.5

Second observer.js patch: fixed a bug that could prevent Gatey Gutenberg blocks from rendering (they stayed invisible but produced no error).

1.3.4

Patched observer.js: eliminated edge-case errors that could appear in the browser console (rendering was unaffected).

1.3.3

Improved licence handling: secondary-domain detection and validation logic have been fixed, ensuring licences activate correctly on all mapped domains.

1.3.2

Flexible reCAPTCHA options: In Gatey → Settings → General you can now choose Classic v3 or Enterprise keys, and switch between google.com and the China-friendly recaptcha.net domain.
Reduced-motion polish: Additional fixes ensure all editor and front-end animations fully respect the user’s “prefers-reduced-motion” setting (follow-up to 1.2.7).
Insecure-host compatibility: All features, including licence validation, now work on plain-HTTP sites lacking the browser Crypto API.

1.3.1

reCAPTCHA upgrade: Gatey now works exclusively with reCAPTCHA Enterprise (v3) keys.

1.3.0

Sign-up attributes unlocked: all standard Cognito attributes are now available in the free plan.
Form-field editor moved down to BASIC: customise field order, labels, and validation rules without a PRO licence.
New field type – country: autocomplete selector with the full ISO list, translated in all 22 Gatey languages.
Enhanced phone_number field: country-code picker now uses the same autocomplete component and localisation as the new country field.

1.2.7

Fixed the Copy Shortcode button in Gatey › Patterns so it now works on sites served over “http://”. Also removed animations from Mantine Select components in the admin UI to prevent tab freezes on Windows when OS-level animations are disabled.

1.2.6

Added a licence-file download guide to the admin screen, plus three JavaScript helpers—Gatey.cognito.toSignIn(), Gatey.cognito.toSignUp(), and Gatey.cognito.toForgotPassword()—for switching screens inside custom blocks.

1.2.5

Filled in the last untranslated UI strings and exposed two client-side helpers: Gatey.cognito.setLanguage() and Gatey.cognito.setDirection() for runtime language or LTR/RTL switching.

1.2.4

Fixed attribute parsing in the [gatey] shortcode; all parameters now load correctly even in edge-case combinations.

1.2.3

Small fixes: the shortcode’s direction attribute now accepts auto, and shortcode previews inside the Elementor editor render correctly even when multiple Gatey shortcodes are placed on the same page.

1.2.2

Added “Auto (by language)” to the Direction setting: the Authenticator now switches to RTL for Arabic or Hebrew and stays LTR for all other languages. You can still override this at any time by selecting LTR or RTL explicitly.

1.2.1

Added a Custom Translations URL field under Gatey › Settings › General. Point it to a JSON file to override any of the 22 built-in languages—or add completely new languages—without touching the code.

1.2.0

The front-end Authenticator screens are now fully localised: choose from 22 languages and switch text direction (LTR / RTL) as needed.

1.1.2

Refined the Settings screen: subscription-management actions now appear only for users who have permission to manage the site’s active plan.

1.1.1

Added the JavaScript chunks that were accidentally left out of 1.1.0; all blocks and admin screens now load correctly.

1.1.0

New on-disk configuration system eliminates all front-end config downloads. Config + weekly licence file now live in the WordPress uploads folder (static exports still refresh the licence weekly). Because downloads are gone, all plans are now flat-priced—there is no longer any “Additional Usage” charge.
The admin screen makes it clear whether the site is linked to a WPSuite workspace and whose workspace it is.

1.0.5

Added new style controls (typography, spacing, colours, etc.) to the Account Attribute block and fixed a configuration-loading bug that could prevent the admin UI from appearing.

1.0.4

Authenticator block: added optional trigger‑button properties — render a button first, and open the Authenticator only after users click it. Perfect for building lean profile pages (see updated Get Started guide).
Account block: now supports full Gutenberg styling controls — alignment, custom HTML tag, box‑shadow, spacing (margin/padding), min‑height, typography (font‑size, line‑height, text‑align) and color (background & text).

1.0.3

Bumped the Authenticator block version to invalidate cached frontend assets—ensures the updated view.js is loaded. No functional changes.

1.0.2

Pro features for an already‑connected site can now be edited even if the WordPress administrator is not logged in to wpsuite.io.
Fixed [gatey] shortcode: the screen, variation, and colormode attributes are now honoured (previously only the pattern defaults were shown).

1.0.1

Authenticator block: added optional “Signing in”, “Signing out” and “Redirecting” message fields, so you no longer need to listen for gatey‑authenticator events for basic feedback. Defaults are empty.

1.0.0

Initial release.