owncloud / owncloud/core

[QA] usecase for storage credentials in config.php needed

Open
#40,069 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

QA:team
Dominant language
PHP
Stars
8.8k
Forks
2.1k
Avg merge
20h 7m
Merged PRs (30d)
41

Description

Seen in 10.10.0 RC2 and 10.9.1

External storages have an option for Credentials hardcoded in config file - This feature allows
to store passwords in config.php
image

We can use this by adding an entry in config.php like this:

'ftpcred' => 'ftp123456data',

Or, to distinguish multiple servers, an array syntax is available:

'ftpcred2' => [ 'localhost' => 'ftp123456data' ],

The feature does not allow to store the user name that belongs to the password. While testing, I found that the name of the current owncloud user is used. This means, that each owncloud user must have an account in the storage server, and all users there have to have the same password.
@pmaier1 It would be great to document a scenario, where this option is helpful. Possibly broken by design?

The docs previously had a different syntax, with sub-keys [ password => ...] which does not work with 10.9.1 or 10.10.0 -> https://github.com/owncloud/docs-server/issues/311

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 reviewing the config.php credential examples in this issue and the earlier docs-server issue #311, then verify the current behavior in an external-storage setup. Done means documenting a valid, useful scenario and the supported syntax, or clearly recording the limitation if the username and password behavior makes the option unsuitable.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
documentation, testing-qa
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.