Creating a Microsoft Teams Manifest

Once the .env file is completely configured, a bot manifest zip file can be created. This is the file users will use to install the bot into their local Microsoft Teams environment.

To create a manifest zip file, use the private POST endpoint, which is provided with the service code. This endpoint will require information from the .env file as input. When executed, the endpoint will generate a manifest zip file in the <BOT_HOME> location.

The response also includes the contents of the manifest.json file (which is packaged within the manifest zip file).

https://<private IP>:<private port>/util/manifest

Input: {"tenant_id" : "xxxxxxxx", "app_id" : "yyyyyyy"}

Output: {"status" : "success", "manifest" : {……}}

An example curl to generate the manifest zip file is:

curl -k -H "Content-type: application/json" -X POST -d '{"tenant_id" : "582b236a-807d-4fe6-a25b-00000000000", "app_id" :"60c8e70e-1411-4b7a-89f4-000000000000"}' https://bothost.acme.com:3988/util/manifest

After a successful post to the manifest endpoint, a zip file named identityiqbot-<version>-manifest.zip is created in <BOT_HOME>.

The manifest zip file contains the manifest.json file, as well as some configuration options such as SailPoint branding colors and outline logos. This can be customized by the users as necessary.

Once the manifest zip file is generated, it doesn't need to be generated again unless there are changes to the bot configuration in the .env file; for example, due to Azure portal changes.

If you face any challenge while generating a manifest zip file, verify the tenant_id and app_id provided are correct.

For more information on the service code, see Installing and Configuring the IdentityIQ Service Code.

You now have successfully created a Microsoft Teams manifest. For next step, refer Configuring API Authentication for Microsoft Teams in IdentityIQ.