cms-dev / cms-dev/cms

Optionally support external login providers for CWS

Open
#112 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1k
Forks
412
Avg merge
6d 10h
Merged PRs (30d)
3

Description

For public CWS instances, a sign-up facility would be useful. We may set one up as a public demo server for IOI 2013.

This would require optionally hashing and salting passwords.

Contributor guide

Open the contributing guide

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

Start by identifying the existing CWS authentication and account entry points; no files or tests are named in the issue. Clarify which external login providers and public sign-up flow are required, then define how password hashing and salting should work. Done should include an agreed provider scope, secure credential handling, and tests for the resulting login and registration behavior.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.