Tidepool Authentication API Deprecation #2596
toddkazakov
started this conversation in
General
Replies: 1 comment 2 replies
-
@toddkazakov Thanks for reaching out. Would you mind clicking on "Create issue from discussion" in the sidebar? Thanks again |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, I am the lead backend developer at Tidepool. In December 2022 we replaced our legacy authentication system with Keycloak. As a result, the existing API endpoints are deprecated, but we noticed that they are heavily used xDrip. As we are trying to completely retire the old system, all applications should migrate to the new OpenID Connect compatible implementation.
We don't have timeframe for the removal of the old APIs, but the way xDrip currently utilizes the APIs puts a strain on the new system (existing APIs act as proxy), because it starts a new auth session every time it requires a fresh token, instead of refreshing the session token directly.
I'll be more than happy to assist with setting up an integration/production environment client for the application. Any OIDC compatible library can be used (e.g. https://github.com/openid/AppAuth-Android). Let me know what's the best way to proceed.
Beta Was this translation helpful? Give feedback.
All reactions