smpallen99/coherence

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

Open

#297 opened on Oct 20, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Elixir (1,259 stars) (220 forks)batch import
help wanted

Description

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.

Contributor guide

Tech stack
elixir
Domain
authenticationbackend
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
ElixirPhoenixauthentication concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
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.