Releases: toolsplus/atlassian-connect-play
0.1.13
0.1.12
Atlassian Cloud APIs will remove any personally identifiable information (PII) to comply with GDPR. This release deprecates userKey
in AtlassianHostUser
and adds userAccountId
in AtlassianHostUser
instead.
We also remove previously deprecated SelfAuthenticationToken code. You should use AP.context.getToken from the client side instead.
0.1.11
A minor update to verify shared secret length when creating a JWT using JwtGenerator
.
If the shared secret length is less than the required 265 bits the current code was throwing an exception. We now assert the length and fail with InvalidSecretKey
if it's too short.
Thanks, @allantl for the contribution!
0.1.10
A minor update deprecating self-authenticated JWTs.
With the addition of AP.context.getToken()
to Atlassian Cloud JS API we can now generate valid JWTs from the client side. There is no need for self-authenticated JWTs anymore. With this release, we mark several components of this library as deprecated. In a second step, we will remove these components in the next release.
0.1.9
0.1.8
Atlassian is moving away from per-installation shared secrets for apps and instead introduces one secret per app. As a result, we have updated AppProperties
to include a secret
value. You should set this in your config file and use PlayAddonProperties
to read it accordingly. Eventually, this will replace the shared secret value in AtlassianHost
. We will remove the shared secret property from AtlassianHost
in an upcoming release.
0.1.7
0.1.6
Extract AtlassianHost and AtlassianHostUser into traits and provide standard case class implementations.
This change allows Cloud and Server add-ons to extend AtlassianHost and AtlassianHostUser types with their own implementation (e.g. on Server to pass around the ApplicationUser associated with a request).
Update Scala to 2.12.6 and Play to 2.6.13.