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

fix LDAP update routine to OC 7 #13759

Merged
merged 1 commit into from
Feb 5, 2015
Merged

fix LDAP update routine to OC 7 #13759

merged 1 commit into from
Feb 5, 2015

Conversation

blizzz
Copy link
Contributor

@blizzz blizzz commented Jan 29, 2015

Supposed to fix #12035 and #12801

Please review and test @butonic @MorrisJobke @PVince81 @jcfischer @fleish

(sidenote: for OC 8 the whole update.php can be dropped imho, as there where no relevant changed. will test and do a PR later).

@scrutinizer-notifier
Copy link

The inspection completed: 3 new issues

@ghost
Copy link

ghost commented Jan 29, 2015

Refer to this link for build results (access rights to CI server needed):
https://ci.owncloud.org//job/pull-request-analyser-ng-simple/8272/
🚀 Test PASSed. 🚀

@MorrisJobke
Copy link
Contributor

👍

@jcfischer
Copy link
Contributor

-99

does not solve the problem, exactly same symptom as before in #12801

@PVince81
Copy link
Contributor

Thing is, if the users were already migrated to new GUIDs then this PR will not repair those. It would only work if the fix is applied before the upgrade to OC 7 (which I believe you did ?)

@MorrisJobke
Copy link
Contributor

😢

@jcfischer So you already update to the stable7 branch before?

@jcfischer
Copy link
Contributor

@PVince81 @MorrisJobke - we did a test upgrade in october/november last year from 6.0.4 or 0.5 to oC 7 EE (possibly the first release) and it went smoothly. We have since upgraded that installation to 7.0.4.

We changed from LDAP uuid to LDAP uid (i.e. email addresses) shortly after our 6.0 deployment with just a few hundred users by manually fixing up the database. There haven't been any UUID users since then.

@MorrisJobke
Copy link
Contributor

@butonic @blizzz It seems that this isn't the only cause for the problem.

@butonic
Copy link
Member

butonic commented Jan 30, 2015

@jcfischer how exactly did you configure oc to use the email adress as the userid in owncloud? in the ldap settings dialog? please describe.

@jcfischer
Copy link
Contributor

@butonic on the LDAP experts page, use the uid attribute

@MorrisJobke
Copy link
Contributor

@butonic Can you review this because this reduces the propability, that something is broken later. Thanks :)

@MorrisJobke MorrisJobke added this to the 7.0.5-next-maintenance milestone Jan 31, 2015
@PVince81
Copy link
Contributor

PVince81 commented Feb 2, 2015

@blizzz can you describe the steps and test cases for this fix ?
I get there is at least two different user id formats ?

@blizzz
Copy link
Contributor Author

blizzz commented Feb 5, 2015

  1. Have 6.0.6/stable6 with LDAP
  2. Configure one LDAP server. Leave Expert tab with defaults.
  3. Do not go to Users tab.
  4. Upgrade to stable7/this branch
  5. Check LDAP config by ./occ ldap:show-config

Before fix: ldap_uuid_user_attribute is empty
After with: ldap_uuid_user_attribute is auto

In case it is neither empty nor auto it's even far less a problem ;)

@DeepDiver1975
Copy link
Member

👍

DeepDiver1975 added a commit that referenced this pull request Feb 5, 2015
fix LDAP update routine to OC 7
@DeepDiver1975 DeepDiver1975 merged commit 3e9d8cc into stable7 Feb 5, 2015
@DeepDiver1975 DeepDiver1975 deleted the fix-12035 branch February 5, 2015 16:05
@lock lock bot locked as resolved and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants