nextcloud / nextcloud/server

User entered credentials can only be set from the web UI

Open
#22,547 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop client: 💻 desktop client: 🤖🍏 mobile enhancement feature: external storage overview
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

  • Setup an external storage that uses "User entered, stored in database" credentials
  • Never access the external storage though the web interface
  • Try to open it on mobile/desktop clients

The web UI checks if credentials still need to be provided in the mount point status coming form ocs/v2.php/apps/files_external/api/v1/mounts?format=json. If that is the case the credentials are asked in a modal and sent back to the server for storing them:
https://github.com/nextcloud/server/blob/f63156976bd647607bd81f2b99786fd7d79ddf7c/apps/files_external/js/statusmanager.js#L389-L427

We ideally should have an OCS API that allows the clients to also implement such a credential dialog.

I would consider this more as an enhancement and document this limitation for now.

Steps to take

  • Server: Implement OCS API to store user defined credentials per mountpoint
  • Android @tobiasKaminsky
  • Desktop @er-vin
  • iOS @marinofaggiana

cc @rullzer

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 with apps/files_external/js/statusmanager.js, especially the mount-status check and credential submission flow linked in the issue, then trace the existing OCS mounts endpoint. Define the server-side API needed to store user-entered credentials per mount point and verify that the client-facing behavior can use it; completion also involves the listed Android, Desktop, and iOS client work.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
api, backend, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.