Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration parameter "enable_certificate_management" without any effect #4452

Closed
jn-se opened this issue Apr 23, 2017 · 3 comments · Fixed by #4800
Closed

Configuration parameter "enable_certificate_management" without any effect #4452

jn-se opened this issue Apr 23, 2017 · 3 comments · Fixed by #4800

Comments

@jn-se
Copy link

jn-se commented Apr 23, 2017

The 'enable_certificate_management' configuration parameter in the config.php does not have any impact on the administration interface. There is no possibility to configure certificates.

Parameter is documented at https://docs.nextcloud.com/server/11/admin_manual/configuration_server/config_sample_php_parameters.html

Steps to reproduce

  1. Add the following line to the config.php

'enable_certificate_management' => true,

Expected behaviour

An administration interface to configure custom certificates.

Actual behaviour

No configuration options shown on the administration pages.

Server configuration

Operating system: Ubuntu 14.04
PHP version: 7.x
Nextcloud version: 11.0.2
Updated from an older Nextcloud/ownCloud or fresh install: Updated

@jn-se jn-se changed the title enable_certificate_management without any effect in config.php Configuration parameter "enable_certificate_management" without any effect Apr 23, 2017
@MorrisJobke
Copy link
Member

This setting was removed and the entries to configure certificates will only show up if this is actually used. They are currently only used by the files external app. So once the files external is enabled the SSL configuration is possible.

@MorrisJobke
Copy link
Member

Documentation is fixed with #4800

@jn-se
Copy link
Author

jn-se commented May 11, 2017

Thank you @MorrisJobke

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants