LDAP user and group backend app is missing [oC 10.0]

ldap
10

#1

I have installed oC 9.x version and successfully integrated it with AD. As there were problems with publishing calendars using WebDAV I have upgraded oC to version 10.0. The problem - as stated in topic subject - is that the LDAP user and group backend app is missing on the apps page.

Steps to reproduce
1. clear installation of oC on Ubuntu server 16.04.02 (using apt-get install)
2. upgrade (using apt-get upgrade)
3. disabled calendar & user ldap (using occ) as occ upgrade returned warnings about apps being incompatible or missing.

Expected behaviour
I was expecting after upgrade to enable 'LDAP .. backend' again and complete AD integration

Actual behaviour
Unfortunately, there is no 'LDAP ... backend' available among apps (enabled or disabled). There is also no such directory in /var/www/owncloud/apps/ folder.

Server configuration
Operating system: Ubuntu 16.04.02 LTS server
Web server: Apache 2.4.18
Database: mysql 14.14
PHP version: 7.0.15
ownCloud version (see ownCloud admin page): 10.0.0.12
Updated from an older ownCloud or fresh install: updated (description above)
Special configuration (external storage, external authentication, reverse proxy, server-side-encryption): external storage enabled for dropbox and SMB integration.

ownCloud configuration

 "system": {
        "updatechecker": false,
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": [
            "***REMOVED SENSITIVE VALUE***"
        ],
        "datadirectory": "\/var\/www\/owncloud\/data",
        "overwrite.cli.url": "https:\/\/xxx.xxx.xxx.xxx\/owncloud",
        "dbtype": "mysql",
        "version": "10.0.0.12",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "localhost",
        "dbtableprefix": "oc_",
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "logtimezone": "UTC",
        "installed": true,
        "ldapIgnoreNamingRules": false,
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpmode": "smtp",
        "mail_domain": "***REMOVED SENSITIVE VALUE***l",
        "mail_smtpauthtype": "LOGIN",
        "mail_smtpauth": 1,
        "mail_smtphost": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpport": "587",
        "mail_smtpname": "***REMOVED SENSITIVE VALUE***",
        "mail_smtppassword": "***REMOVED SENSITIVE VALUE***",
        "maintenance": false,
        "loglevel": 2
    }

ownCloud log (data/owncloud.log)

Integrity status for oC9+

No errors have been found.

Owncloud 10 and ldap-auth
LDAP user and group App not present
#2

Found info ... LDAP integration is not yet available for version 10.0 ... I've found it few seconds after sending previous post.


#3

Same here! Could you post where is this information about LDAP integration not yet available for version 10.0?

Is it normal? A version with an important feature as LDAP authentication got released?

--

EDIT: I just found it on another post here in central.


#4

This is very urgent to us, too - our system is down because it's not supporting LDAP.
When will the LDAP app be available for oC 10?
Is there any quick fix / workaround?


#5

Hi people!

Where can I get the version v9.1.5-1.1 ?

The system is down because it's not supporting LDAP. So, I need to restore v9.1.5-1.1 and the database backup for this version.

APT repository just have the latest version, v10.0.0, called 'stable'. Normally, the stable version has all features that is in a previous version. I think the reposity should have at least the lastest minor version from version 9, or something like that.

Tks.


EDIT: we can get a tarball here

https://download.owncloud.org/community/owncloud-9.1.5.tar.bz2


#6

Hi,

I did also fall knee deep here..

Is it possible to downgrade to 9.1.5? or when is the ldap module expected to be ready?


#7

Just some notes:

  1. Never upgrade to the next major release without doing any backups or having a rollback plan
  2. Never upgrade a productive system to the first release of a major release (especially not directly on the release day)
  3. Check if all features / apps you currently need are available in/for that major release
  4. Downgrading is not possible without reverting to a previous done backup
  5. Older repositories (e.g. for 9.1) are linked at https://owncloud.org/changelog/

About the missing ldap app:

AFAIK most apps where moved to the new marketplace so just give them some time to sort out everything like the availability of these apps. I think its a good step forward to not include all apps like the user_ldap app in the release. This makes the package more modular and doesn't deploy unneeded stuff on every installation out there.


#8

That's actually also my advise, but how do you know it's an major update? I just did "sudo apt-get update/upgrade"... It should at least be mark as hold so it doesn't install automatically. Maybe it's now time to move to nextcloud. Every major owncloud upgrade was a lot of trouble. And also have a look at seafile guys, I'm using it more than two years and had not any problem with any update. Quite awesome.


#9

Personally i'm informing myself about the software i'm using and the release cycles and new releases. So i know whats a major release and also know if i should do an update / upgrade or not.

You also have to chance to use the 9.1 repositories at:

https://download.owncloud.org/download/repositories/9.1/owncloud/

which doesn't push you to the next major release once it is out. With that you can control the time you're jumping to the next release on your own but still receive updates for your current used version.


#10

This is a very important information!!! It should be on the download page of website. When we click in Downloads we get the page with instruction to add a "stable" repository.

Hey! At this point the website could explain that there are repositories based on major releases! So, admins can choose what version they want.

https://download.owncloud.org/download/repositories/

And, finally, this model where the stable repository changes between major versions is very strange! Stable could be named "latest", couldn't?

I've restored the backup with 9.1 version, application and database. But, the .deb package froze on installed state and I can't touch this! I'm goingo to install a new server and wait for LDAP support on v10. Then, I will migrate.

Tks.


#11

Mhhh, if you have a look at:

https://owncloud.org/install/#edition

and click on the "Packages" tab you will see the following text on the right side:

Channels:
We offer Release Channels to track specific branches like Beta's or older stable branches

Each version entry on the https://owncloud.org/changelog/ page has also a link to this release channels in the form of:

Learn more about Release Channels.

If you have feedback about the visibility of this information they are probably happy about these at e.g. https://github.com/owncloud/owncloud.org/issues


#12

On a stable Debian system you expect to be able to do apt-get upgrade safely. Owncloud is probably one of the very few exceptions from this rule.

I got used to the fact that every single minor upgrade required manual invocation of occ to perform actual upgrade. But I really did not expect that you would deliver untested and incomplete release on STABLE channel...

You should name it "daily" or "experimental" so we knew to stay away from it.


#13

I completely agree with @bartek_o and others on this issue. At my company we apply unattended upgrades on all but a few servers to keep them up to date and secure with the latest patches. So when our OwnCloud server was in maintenance mode this morning I logged in and did the regular update routine using the occ command. Little did I know that this would result in an unusable instance due to the unavailability of LDAP and 2FA.

Yes you can stick to a single major release as @kljhlkhglklfgh suggests, but this is definitely not as clear as it could be and not quite the default if you go for an installation through OwnCloud's repositories. All in all I'm not quite happy with OwnCloud today, which is unfortunate since I like the product but it's still in an acceptance stage at my company.


#14

An indicator how many days finishing the LDAP module needs would be nice. So I know if it's worth waiting...


#15

user_ldap will arrive in the next days via the marketplace - this was communicated via the release notes

-> https://github.com/owncloud/core/issues/27768

Thats the info which is available to us users.


#16

Ouch - this kind of takes this version of the table for enterprise.


#17

IMHO the first releases of a major version never should be on the table for enterprise (even not on productive home environments).


#18

True - but leaving behind a feature like authentication really makes it tough for me, who was subscribed to the "stable" channel. I would recommend new releases get put in the beta channel. To keep with patching a INET facing application, I have updates occur automatically. Until now, things have been patched without issue, and then things got updated to the new version, which left behind the ability to authenticate users. I can understand new features not working, but things like authentication shouldn't break.


#19

From what i can see pushing 10.0 to the "stable" channel was a mistake as it was reverted only a few hours later. They never did that before and waited a few months (e.g. for x.0.1 or x.0.2) before pushing the next major release into the stable channel.


#20

Ahhh - got ya. We're still in testing/dev, and I would always snapshot the VM before making changes, and have backups, but this update certainly was a surprise.