loopbackio / loopbackio/loopback-connector-sqlite3
Does not return proper accessToken
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Sqlite3 connector gives following when logging in:
Access token stored in the database is correct, but returned id is the id of accessToken instead of the token itself.
{
"id": 1,
"ttl": 1209600,
"created": "2016-02-22T13:32:31.305Z",
"userId": 1
}
When using db(in-memory) for storing access tokens it gives following correct result.
{
"id": "APXMEsHyWmZmXBgi5vAMfWwVfd72nyaXCihskDvqvQILjoliSfGRlcS9MDrtkrrR",
"ttl": 1209600,
"created": "2016-02-22T13:33:41.987Z",
"userId": 1
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce a login using the SQLite3 connector and compare its returned access-token object with the correct in-memory result shown in the issue. Trace how the stored access token is read and returned; done means the SQLite3 response exposes the token string as id while preserving ttl, created, and userId.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100