Skip to content
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

API v3: Secure API does not accept string ID #313

Closed
quentinlesceller opened this issue Jan 22, 2020 · 2 comments
Closed

API v3: Secure API does not accept string ID #313

quentinlesceller opened this issue Jan 22, 2020 · 2 comments
Labels
bug Something isn't working

Comments

@quentinlesceller
Copy link
Member

Similar to #312 except a bit more annoying this time.
Once initialized, the secure API does not accept ID as string.

{ 
   "id":"3",
   "jsonrpc":"2.0",
   "method":"encrypted_request_v3",
   "params":{ 
      "nonce":"2994319f73303015805b22c3",
      "body_enc":"M1X8zvf0MTjJ8uYkEOWlxKcRvz16g+PtiKNdttYddlMapOzGi8gV7yJrsOYdDkaLhVP3Y3o8LTGuVW56EpV+s8Tjgxy9DWoPIiW1vMm5V0ITvXX2enZVgswmkvNjnkhjTB1tydpv"
   }
}
{
  "error": {
    "code": -32002,
    "message": "Encrypted request format error: invalid type: string \"3\", expected u32"
  },
  "id": 1,
  "jsonrpc": "2.0"
}
@quentinlesceller quentinlesceller added the bug Something isn't working label Jan 22, 2020
@quentinlesceller
Copy link
Member Author

Preparing a PR for that one.

@yeastplume
Copy link
Member

Fixed via PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants