Breaking Changes Planned for OAuth /token Response
Published
A breaking change is planned for the OAuth /token Response. We will be removing the
tenant_id
and tenant_name
properties from the SKY API OAuth service /token
endpoint response at the end of July 2019. See our Changelog for more information.
News
SKY Developer Announcements
06/20/2019 2:33pm EDT
Leave a Comment
The use case for us is that we tie their subscription info to the tenant ID currently. This is set up before they authenticate. To do the same going forward, the client would need access to their environment ID.
However, I'd like to understand your specific scenarios and how you are using these values. I'll reach out directly to learn more.
What's next the environment_id as well? There's already barely enough information developers can use to make apps with multi-tenant capability to uniquely identify sessions across users. Do these kind of breaking changes on api/v2 not v1. As Steven said, you don't make breaking changes to an API that only has 1 version.
I may as well stop development on my application if this change is made.
-Jackson
Not only is this a breaking change, it's an app killer.
Also, from Ben Lambert only a few months ago in quite involved post:
"So if you have the option, we'd recommend getting in the habit of using the environment_id and user_id combination as your correlating values, but the older model of tenant_id + user_id will continue to work for quite a while (and we'll manage the internal interpretation/implementation of access tokens on our end)." (My bold.)
I would suggest reconsidering this move. And when is Blackbaud going to start versioning, rather than breaking, the SKY API?? You're the only organization I know that regularly releases breaking changes. Virtually everyone else versions to maintain workability.
This really does make me question Blackbaud's comprehension of API best-practice.
Steve Cinquegrana | CEO and Principal Developer | Protégé Solutions