Skip to content

Tidepool Integration: Authentication Changes #3890

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tjotala opened this issue Mar 18, 2025 · 3 comments
Open

Tidepool Integration: Authentication Changes #3890

tjotala opened this issue Mar 18, 2025 · 3 comments

Comments

@tjotala
Copy link

tjotala commented Mar 18, 2025

Tidepool is planning to deprecate our legacy authentication APIs in favor of new OAuth2 / OpenID Connect standards based APIs. You can find the documentation here:

https://developer.tidepool.org/TidepoolApi/#tag/Authentication/operation/Authorize
https://developer.tidepool.org/TidepoolApi/#tag/Authentication/operation/ObtainToken

We see that AndroidAPS is currently using the legacy authentication APIs: https://github.com/nightscout/AndroidAPS/blob/master/plugins/sync/src/main/kotlin/app/aaps/plugins/sync/tidepool/comm/TidepoolApiService.kt#L28-L29

Please contact us to discuss migration to the new authentication APIs:

https://developer.tidepool.org/
info@tidepool.org

Sincerely,

Tapani Otala
VP, Engineering
Tidepool

@MilosKozak
Copy link
Contributor

Image
@tjotala what is allowed clientId ?
"AAPS" didn't pass

@MilosKozak
Copy link
Contributor

tha same for redirectUri "aaps://callback/tidepool"

@toddkazakov
Copy link

Hi @MilosKozak, here are the client details:

Integration:

Production:

Let me know if I can assist you in any other way. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants