Releases: descope/go-sdk
Releases · descope/go-sdk
v0.9.3
Breaking changes
- Rename of External ID to Login ID: In order to clarify and align the various user identifiers used in our system - we've decided to rename
ExternalID
toLoginID
. - Rename Tenant Association attribute:
UserTenants
has been renamed toAssociatedTenant
. This is used in both Users and Access Keys.
Enhancements
- SCIM support 🚀 : We now support SCIM related actions, including: user updates, group updates, user creation, and more! This means you can automatically sync users in Descope with your own IdP, and not have to deal with building a custom automation around it.
- Support Access Keys management via API: Actions for Access Keys management, including:
create
,update
,delete
,load
,search
,deactivate
andactivate
. - User picture in user response: There are some providers that return the user's picture in the response. It is now also returned in the
UserResponse
object.
Bug fixes
- Refresh JWT parsing from cookie: In our latest release, we updated that we always include the Refresh JWT in our verification response. When working with cookies, the parsing failed and it returned an empty Refresh JWT. This was quickly found and fixed.
v0.9.2
Breaking changes
- Session JWT in verification response: Up until now, the Session JWT was sent in a cookie by default. We decided to change it so that
the Descoper has the power to control whether the Session JWT is handled by the calling function or sent in a cookie (using theSessionJWTViaCookie
flag).- By default, the Session JWT is returned to the calling function. This is because it can grow to a relatively big size (especially when using Authorization and Custom Claims).
- Use cookie if the Session JWT is relatively small (less than 1KB); examples for the latter are available in the
examples
folder in this repo.
- JWT validation timeframe: As the JWT validation process is time sensitive (both for creation and expiration), we have decided to increase the difference we allow between Descope and the Descoper. It is now set to 5 seconds.
Enhancements
- Refresh JWT will always be available in verification response: We adjusted our authentication verification response to always include the Refresh JWT.
- Fixed Enchanted Link example: As mentioned in the previous release, we updated one of Enchanted Link's attribute's name, which required an update of the example it's used in.
- API to load all tenants: New API that returns a list of all the tenants in the project.
- API to load user by JWT Subject: New API that returns a user object, queried by its JWT Subject.
- Readme updates: Updated the README of the repo, to make newcomers' lives even easier than before!
v0.9.1
Breaking changes
- Enchanted Link attribute change: Updated the
identifier
attribute tolinkId
, to make it clearer for the Descoper to use.
Enhancements
- Key Response structure update: A
v2
of the key response API; in order to support other frameworks, such as OpenID Connect, the key response's structure was updated, and keys are now a sub-attribute ofkeys
.- Format in
v1
:[{...}]
- Format in
v2
:{"keys": [{...}]}
- Format in
- Support Roles via API: Actions for Role management, including:
create
,update
,delete
andloadAll
.