auth-tool-cloudbase

Use manageAppAuth with action patchLoginStrategy and a short patch object, for example {"patch": {"email": true}}. The tool reads the current strategy, merges your change, and writes it back, so you do not need to build a full ModifyLoginConfig payload.

Call queryAppAuth with action getPublishableKey to retrieve the existing publish_key, or manageAppAuth with action ensurePublishableKey to create one if none exists. The publishable key is required before writing frontend Web auth code.

The auth tool handles management-side login only, such as status, start_auth, and set_env. queryAppAuth and manageAppAuth handle application-side configuration like login methods, providers, publishable keys, and client settings.

No. Anonymous login is disabled by default for new environments, and inactive existing environments have it automatically disabled. Enable it explicitly with patchLoginStrategy only when unauthenticated access is required, noting anonymous users cannot call AI models by default.

Skip provider setup when the required login method and publishable key are already confirmed in an existing project. In that case, return to the active login and register handlers and finish the user flow instead of re-querying provider status.