Cloud ID in Connect lifecycle HTTP request payload

Forge Adopting Forge from Connect
, ,
1

Hi. We released the Forge version of the plugin (with connect modules) and noticed that the Connect lifecycle HTTP request payload now has a cloudId field. However, it is not in the documentation.
Can we assume that this field will be present in all installation payloads?
If so, is there a chance that it will be added to the documentation (as it was done for installationId)?
Thanks

2

Hi @SemyonGashchenko ,

We don’t currently have plans to remove cloudId from the payload, but installationId is what you should use as the identifier. We had a couple of gaps in our APIs where cloudId had to be supplied but I believe these are all closed now - please let us know if you encounter APIs that require the cloudId.

3

Hi @jhazelwood. Thanks for the reply. Right now we use cloud ID to build context for offline user impersonation. See How to use Forge offline user impersonation from Remote - #2 by Ilnar
Previously we used client key for identification, but it changed when performing backup/restore of Jira instance, which resulted in loss of customer plugin data. So we switched to using cloud ID as a stable identifier for tenant.

4

Thanks. Offline user impersonation is one of the places you’ll need it.

1 Like