smpallen99/coherence

plug Coherence.Authentication.Token isn't the same as Coherence.user_token(@conn)

Open

#297 创建于 2017年10月20日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)Elixir (1,259 star) (220 fork)batch import
help wanted

描述

Correct me if I'm wrong, but these are two different things. You can't take a token from Coherence.user_token function and send it in header to Coherence.Authentication.Token plug, because they have different storage.

The best way is to marry them, the ok way is to describe this case in README. It took about an hour of digging in source codes to figure out this.

贡献者指南

技术栈
elixir
领域
authenticationbackend
议题类型
documentation
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
ElixirPhoenixauthentication concepts
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Investigate the source code for Coherence.Authentication.Token plug and the Coherence.user token/1 function to understand the difference in token storage. Determine if it is feasible to unify them or if the README should be updated to document the distinction. Review any existing comments or discussions in the issue to see if a maintainer has provided guidance.