Skip to content
This repository has been archived by the owner on Mar 22, 2022. It is now read-only.

Token encoding is not using the idField option. #107

Closed
ekryski opened this issue Mar 16, 2016 · 2 comments
Closed

Token encoding is not using the idField option. #107

ekryski opened this issue Mar 16, 2016 · 2 comments
Labels
Bug
Milestone
0.6

Comments

@ekryski
Copy link
Member

ekryski commented Mar 16, 2016

idField option (which by default is _id and why you don’t need to provide it) is not being respected when ​_encoding_​ the JWT but ​_is_​ when it is decoded.

This line is 👍

This line is 👎
@ekryski ekryski added the Bug label Mar 16, 2016
@ekryski
Copy link
Member Author

ekryski commented Mar 16, 2016

Somewhat related to #103

This was referenced Mar 17, 2016
Closed
Closed
ekryski added a commit that referenced this issue Mar 18, 2016
@ekryski
Token encoding now uses the idField option. Closes #107. Closes #103
3d48460
@ekryski ekryski modified the milestone: 1.0 release Mar 19, 2016
@ekryski ekryski mentioned this issue Mar 21, 2016
Merged
10 tasks
@saiichihashimoto
Copy link
Contributor

I was just about to report this issue!

@ekryski ekryski modified the milestones: 1.0, 0.6 Mar 26, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Bug
Projects
None yet
Milestone
0.6
Development

No branches or pull requests
2 participants
@ekryski @saiichihashimoto