auth-tool-cloudbase

Configure CloudBase authentication providers by activating this skill to manage login methods across web, mini programs, native apps, and backend flows using DescribeLoginConfig and ModifyLoginConfig APIs. It centralizes provider settings for quick enablement and verification.

CloudBase supports enabling and managing SMS, Email, WeChat Open Platform, Google, Anonymous, Username/Password, OAuth, SAML, and CAS login methods. This skill governs activation and configuration for these providers across multiple platforms.

Yes, CloudBase authentication setup supports native apps and backend HTTP API flows. This skill manages provider activation and verification across these environments using the CloudBase EnvId to implement the configuration workflow.

The best way to sequence CloudBase login provider activation is to read the Activation Checklist provided by this skill before implementing UI or backend flows, ensuring proper configuration and verification across platforms via MCP tools.

CloudBase authentication setup is often fragmented because provider settings span multiple platforms and services. This skill solves the problem by centralizing provider configuration, enabling quick management of login methods via MCP tools calling callCloudApi.

Yes, you need a CloudBase EnvId to manage authentication providers. This skill relies on the EnvId and uses APIs like DescribeLoginConfig, ModifyLoginConfig, and ModifyProvider to implement the provider configuration and verification workflow.