Last updated Nov 22, 2024

Connect Active API migration

These API migrations are active and affect API behavior:

Migration Key	Purpose / Changed behavior	Allowed values
`context-qsh`	Controls whether context JWTs include a qsh claim. The claim is a fixed value, which does not validate with regular qsh validation.	`true`: Context JWTs include a fixed qsh value. Also, it signals to Atlassian that you have completed migration and are ready for this to become permanent. `false`: The app continues to receive context JWTs that do not contain a qsh value until the end of the transition period. &#91omitted&#93: The app receives context JWTs that do not contain a qsh value until the end of the transition period. Also, it signals to Atlassian that you have not started work on the migration.
`signed-install`	Controls whether install/uninstall lifecycle events will be signed with asymmetric JWT.	`true`: JWT token in lifecycle events will be signed with RS256 algorithm and it can be validated using a corresponding publicKey. Additionally, it signals to Atlassian that you have completed migration and are ready for this to become permanent. `false`: The app will continue to receive install events signed with a shared secret until the end of the transition period. [omitted]: The app will continue to receive JWTs signed with a shared secret in lifecycle events until the end of the transition period. Additionally, it signals to Atlassian that you have not started working on completing the migration.