closeio / closeio/socketshark

Multiple authentication method

Open
#58 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
128
Forks
12
Avg merge
3d 16h
Merged PRs (30d)
6

Description

Hi, do you have a plan for allowing multiple authentication methods? For example, some users can authenticate with JWT and others with cookie session or ticket.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named in the issue. Start by locating the authentication and WebSocket routing entry points, then determine how JWT, cookie-session, and ticket authentication could coexist; done means users can use different methods within the same system.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, redis
Domain
authentication, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.