Question 1

How to set up Google login with Payload Auth Plugin?

Accepted Answer

Configure OAuth credentials in the plugin options by following the documentation; it involves adding provider keys and callback URLs similar to standard OAuth flows. Ensure your Payload instance is properly set up to handle redirects.

Question 2

Payload Auth Plugin vs custom auth for Payload CMS?

Accepted Answer

This plugin saves time with pre-built features like social login and session management, but custom auth offers more control. Choose based on project scale—plugin for rapid development, custom for unique requirements.

Question 3

Does it support JWT tokens or only sessions?

Accepted Answer

It uses token-based sessions as per the key features, but the exact token type (e.g., JWT) isn't specified; check the documentation for implementation details and customization options.

Question 4

How to add phone number field to users?

Accepted Answer

Extend the customizable user model by modifying the plugin configuration to include new fields like phone number, then update validation and UI components accordingly in your Payload setup.

Question 5

Is multi-tenant support hard to configure?

Accepted Answer

No, it's designed to be straightforward with tenant isolation built-in; setup involves defining tenant-specific settings in the config, but review the docs for best practices on data separation.

Question 6

Can I use this for a mobile app backend?

Accepted Answer

Yes, if the backend is built with Payload CMS, as the plugin provides API endpoints for authentication that can be consumed by mobile apps, though frontend integration requires additional work.

authsmith / payload-auth-plugin

What is authsmith / payload-auth-plugin?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions