KAGEOS GUIDES
Login & authentication
Configure login providers and verify callback addresses.
Sign in to your instance
Use the instance URL and account supplied by your administrator. The initial self-hosted administrator is system; credentials come from deployment output.
Administrators configure third-party login under System settings → Login settings. Configuration is stored in the database and takes effect without a restart. Only enabled providers with complete required fields appear on the login page.
Choose a provider
| Provider | Required information |
|---|---|
| kageos unified authentication | Client ID, Client Secret and an allowlisted callback URL |
| WeChat Official Account QR login | AppID, AppSecret and message Token |
| WeChat Open Platform | Website application AppID, AppSecret and callback URL |
Unified authentication and direct Official Account integration use different credentials and callbacks.
Configure and verify
- Prepare the application at the provider.
- Copy the exact callback URL shown in settings to the provider console.
- Save required fields and enable the provider.
- Test sign-in in a separate browser session.
Direct Official Account login currently supports plaintext message mode, not AES compatibility or secure mode. QR codes expire after five minutes.
First sign-in and troubleshooting
New external identities confirm a unique user code within the instance. Matching nicknames or unverified email addresses do not automatically merge accounts.
If a button is missing, check enablement and required fields. If callbacks fail, compare the protocol, host and path. Refresh expired QR codes. Connector authorization grants access to external data; it is not a login provider.
Keep application secrets out of public documents, browser code and screenshots.