Migrate authentication from Auth0 to SmartTub IDP #66
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SmartTub moved new accounts to their own IDP endpoint. This change: - Uses new /idp/signin endpoint instead of Auth0 - Parses new token response format - Re-authenticates on token expiry (no refresh endpoint available) - Removes jwt dependency (manually decode ID token for account_id) Fixes home-assistant/core#156317
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
SmartTub moved new user accounts to their own IDP endpoint, breaking authentication for these accounts. This change migrates from Auth0 to the new SmartTub IDP.
Changes
https://api.smarttub.io/idp/signin(was Auth0/oauth/token){"token": {...}}custom:account_idclaim in ID token (was Auth0 claim)jwtdependency (manually decode ID token for account_id)Testing
Fixes home-assistant/core#156317
Thanks @xags for the patch