fix(oauth): correct OAuth implementation to match bunq documentation
This commit is contained in:
18
changelog.md
18
changelog.md
@@ -1,5 +1,23 @@
|
||||
# Changelog
|
||||
|
||||
## 2025-07-22 - 3.0.8 - fix(oauth)
|
||||
Correct OAuth implementation to match bunq documentation
|
||||
|
||||
- Removed OAuth mode from HTTP client - OAuth tokens use normal request signing
|
||||
- OAuth tokens now work exactly like regular API keys (per bunq docs)
|
||||
- Fixed test comments to reflect correct OAuth behavior
|
||||
- Simplified OAuth handling by removing unnecessary special cases
|
||||
- OAuth tokens properly go through full auth flow with request signing
|
||||
|
||||
## 2025-07-22 - 3.0.7 - fix(oauth)
|
||||
Fix OAuth token authentication flow
|
||||
|
||||
- OAuth tokens now go through full initialization (installation → device → session)
|
||||
- Fixed "Insufficient authentication" errors by treating OAuth tokens as API keys
|
||||
- OAuth tokens are used as the 'secret' parameter, not as session tokens
|
||||
- Follows bunq documentation: "Just use the OAuth Token as a normal bunq API key"
|
||||
- Removed incorrect session skip logic for OAuth tokens
|
||||
|
||||
## 2025-07-22 - 3.0.6 - fix(oauth)
|
||||
Fix OAuth token private key error
|
||||
|
||||
|
Reference in New Issue
Block a user