Normalises and stores the login and signup configuration, then returns it with the recalculated form field definitions.
The payload is passed through the auth settings formatter, so unrecognised keys are dropped and each field is coerced to its expected shape. The saved settings are also written to a week-long cache used by the front-end auth screens.
Endpoint
Method:
POSTPath:
/admin/auth-settingsEdition: PRO
Controller:
ProAdminController@saveAuthSettingsRoute source:
fluent-community-pro/app/Http/Routes/api.php:15Controller source:
fluent-community-pro/app/Http/Controllers/ProAdminController.phpRequires the FluentCommunity community-admin permission (or a WordPress super admin).
Requires FluentCommunity Pro.
Live sample
The request and response below were recorded against a running FluentCommunity install and then anonymised — member names, emails, avatars and post content are fictional, and long collections are trimmed to a few entries.
POST Save Auth Settings
Normalises and stores the login and signup configuration, then returns it with the recalculated form field definitions.
Controller: ProAdminController@saveAuthSettings
Route source: fluent-community-pro/app/Http/Routes/api.php:15
Authorizations
WordPress Application Passwords — use Basic auth with username:application_password.
Request Body
Responses
Successful response