This topic describes how to publish and access a Copilot application.
Copilot application publishing
After you configure a Copilot application, click the Publish button in the upper-right corner of the designer to publish the application to a development or production environment.
Publishing from the development environment
The development environment is used for testing during the development phase. After you publish the application, you can find its development environment address in the application's environment information.
Publish to a production environment
The production environment is used for real business scenarios to serve end users. After you publish the application, you can find its production environment address in the application's environment information.
Access a Copilot application
After a Copilot application is published, an application address is generated. You can access the application by entering the URL in a browser or through SDK integration.
Independent access
You can enter the URL in a browser to access the Copilot application independently. Different identity authentication methods are available based on the application's logon configuration.
Anonymous access
No authentication is required. However, the anonymous user permission group must have sufficient access permissions to access the application. For more information, see Anonymous users and Permission group management.
Logon access
Authentication is performed on the logon page. The logon method depends on the identity source configuration.
SDK integration access
You can quickly integrate a Copilot application into Android and iOS apps using the SDK provided by Mobi. Different identity authentication methods are available based on the application's logon configuration and publishing environment. For more information about SDK integration, see Android SDK integration and iOS SDK integration.
Anonymous access in a development environment
No authentication is required. However, the anonymous user permission group must have sufficient access permissions to access the application. For more information, see Anonymous users and Permission group management.
Logon access in a development environment
Authentication is performed on the logon page. The logon method depends on the identity source configuration. For more information, see End user access and Identity source management.
Anonymous access in a production environment
No authentication is required. However, the anonymous user permission group must have sufficient access permissions to access the application. Note: When you configure the SDK, do not pass in a JWT Token. If a JWT Token is passed in, identity authentication is performed based on the JWT Token, and anonymous access is disabled.
Logon access in a production environment
If a Copilot application in a production environment does not allow anonymous access, authentication is performed using a JWT Token. First, go to the Mobi console and choose Users and Permissions > Identity Sources. Create and enable a JWT identity source. Ensure that the permission group corresponding to the identity source has sufficient access permissions. Then, call the GenerateNativeUserToken API to generate a JWT Token and pass it to the SDK. Note that the JWT Token has a time-to-live (TTL) of 300 seconds. Before the token expires, call the RefreshNativeUserToken API to obtain a new one. Finally, use the updateAccessToken method exposed by the SDK to set the new JWT Token.