rclone / rclone/rclone

Single Sign On Support for Seafile

Open
#7,687 4 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Remote: Seafile
Dominant language
Go
Stars
59.8k
Forks
5.4k
Avg merge
2d 14h
Merged PRs (30d)
48

Description

The associated forum post URL from https://forum.rclone.org

https://forum.rclone.org/t/single-sign-on-support-for-seafile/45197

What is your current rclone version (output from rclone version)?

rclone v1.67.0-beta.7788.ff855fe1f

  • os/version: Kylin V10 (64 bit)
  • os/kernel: 6.7.9-amd64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.22.1
  • go/linking: static
  • go/tags: none
What problem are you are trying to solve?

Single sign on support for Seafile

How do you think rclone should be changed to solve that?

I am not sure, but perhaps it can be solved by fetching login credentials via browser, like the process for OneDrive. The Seafile client itself launches a browser window to redirect me to the login page of the self-hosted service.

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

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 reading the associated forum post and reviewing how rclone handles browser-based authentication for OneDrive. Identify the existing Seafile integration and determine the required SSO flow for self-hosted services. Done means a reviewed design and working support for the requested login flow, with appropriate validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
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.