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

LDAP user sync does not work (here) #4433

Closed
2 of 7 tasks
cklabautermann opened this issue Jul 12, 2018 · 5 comments
Closed
2 of 7 tasks

LDAP user sync does not work (here) #4433

cklabautermann opened this issue Jul 12, 2018 · 5 comments

Comments

@cklabautermann
Copy link

cklabautermann commented Jul 12, 2018

  • Gitea version (or commit ref): 1.4.0, 1.4.2,1.4.3,1.5.0RC2
  • Git version: 2.7.4-0ubuntu1.4
  • Operating system: Ubuntu Server 16.04.4 AMD64
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

my auth setup includes

  • bind to a ms-AD unencrypted
  • with a RO userid
  • a user search base where the users are
  • a user filter pointing to a group in a completely different OU
  • user synchronisation activated (at least marked)

Things that work:

  • manually adding a user and authenticating them via LDAP. If a user is not member in the filter group, they can not login.

Things that do not work:

  • users in my filter group being automatically synchronized

Additionally all users authenticating via ldap get deactivated if I dare to execute a manual user synchronisation via web frontend.

Can anybody tell me what I am doing wrong?
Not sure if screenshots could help here but I can upload some on demand.

Thanks,
Claudio

@cklabautermann cklabautermann changed the title LDAP user synch does not work (here) LDAP user sync does not work (here) Jul 12, 2018
@stale
Copy link

stale bot commented Jan 18, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Jan 18, 2019
@lunny
Copy link
Member

lunny commented Feb 7, 2019

@cklabautermann is this still a problem?

@cklabautermann
Copy link
Author

@lunny yes, unfortunately it still does not work. Can you help?
Thanks in advance

@stale stale bot removed the issue/stale label Feb 7, 2019
@lunny lunny added the type/bug label Feb 7, 2019
@stale
Copy link

stale bot commented Apr 8, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Apr 8, 2019
@stale
Copy link

stale bot commented Apr 22, 2019

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed Apr 22, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants