You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- BitBucket
- Cleans up primary email logic
- Moves `email` key from `from_id_token_payload` to `from_user_info_api` in `raw_user_info_from_provider`
- Github
- Changes `id` field access to be concrete to be in-line with API Spec
- Adds raw user info to output
- Makes primary email logic consistent with BitBucket
- LinkedIn
- Changes `sub` field access to be concrete to be in-line with API Spec
- Adds raw user info to output
Co-authored-by: Viraj Kanwade <[email protected]>
- If you are using `get_user_id`from`thirdpartypasswordless` recipe:
813
-
824
+
814
825
Before:
815
826
```python
816
827
from supertokens_python.recipe.thirdpartypasswordless.syncio import get_user_by_id
@@ -1022,7 +1033,7 @@ With this update, verify_session will return a 401 error if it detects multiple
1022
1033
)
1023
1034
```
1024
1035
1025
-
- In the session recipe, if there is an `UNAUTHORISED`or`TOKEN_THEFT_DETECTED` error, the session tokens are cleared in the response regardless of if you have provided your own `error_handlers`in`session.init`
1036
+
- In the session recipe, if there is an `UNAUTHORISED`or`TOKEN_THEFT_DETECTED` error, the session tokens are cleared in the response regardless of if you have provided your own `error_handlers`in`session.init`
1026
1037
1027
1038
## [0.17.0] - 2023-11-14
1028
1039
- Fixes `create_reset_password_link`in the emailpassword recipe wherein we passed the `rid` instead of the token in the link
0 commit comments