Skip to content

LDAP Integration Not Functional  #236

Description

@ResearchMark

linuxserver.io

Clean install of Nextcloud through unraid community app store, latest stable version php 7. Unable to use LDAP integration as buttons do not have any response. No errors on docker logs or Nextcloud logs level 2. Tested LDAP configuration on clean install of official Nextcloud docker image and Owncloud both worked smoothly. Clicking Test DN or save credentials does nothing. Unable to complete setup as continue button grayed out.


Expected Behavior

Allow to enter and verify LDAP settings.

Current Behavior

You can enter in the required info but clicking on any options does nothing.

Steps to Reproduce

  1. Enable LDAP/AD Integration app and attempt to enter info

Environment

**OS: UNRAID
**CPU architecture: x64
**How docker service was installed: Preinstalled via unraid

Command used to create docker container (run/create/compose/screenshot)

Using UNRAID community apps install

Docker logs

Brought to you by linuxserver.io

To support LSIO projects visit:
https://www.linuxserver.io/donate/

GID/UID

User uid: 99
User gid: 100

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 40-config: executing...
[cont-init.d] 40-config: exited 0.
[cont-init.d] 50-install: executing...
[cont-init.d] 50-install: exited 0.
[cont-init.d] 60-memcache: executing...
[cont-init.d] 60-memcache: exited 0.
[cont-init.d] 70-aliases: executing...
[cont-init.d] 70-aliases: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 70-aliases: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

Activity

  1. github-actions commented on Feb 23, 2022

    @github-actions

    Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

  2. github-actions commented on Mar 26, 2022

    @github-actions

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

  3. chrisbley commented on Mar 27, 2022

    @chrisbley

    same issue here! is this issue going to be addressed? cheers for all the good work!

  4. BoavaNet commented on Mar 29, 2022

    @BoavaNet

    ya having same issues here, damn was hopping to keep all my Authentication with LDAP

  5. NobleKangaroo commented on Apr 13, 2022

    @NobleKangaroo
    Contributor

    Same issue here. This used to work in the past, but multiple folks have had issues related to routing (1, 2, 3, 4, 5) since Nextcloud 20.0 released.

    This looks to be related to a PR for Nextcloud 19 to clean up and standardize the NGINX config and remove redundancy. However it was found that the new config has issues with the legacy ajax endpoints of the user_ldap app. This line was subsequently reverted and added back to the NGINX config's documentation for 20.0 and later, and other projects such as NixOS added the line to their configs.

    Compared to the Nextcloud 19.0 documentation for an NGINX setup (which the Linuxserver.io container uses), the Nextcloud 20.0 through latest documentation have the aforementioned line added to resolve issues with legacy AJAX endpoints:

    # Required for legacy support
    rewrite ^/(?!index|remote|public|cron|core\/ajax\/update|status|ocs\/v[12]|updater\/.+|oc[ms]-provider\/.+|.+\/richdocumentscode\/proxy) /index.php$request_uri;

    This line is currently missing from this container's NGINX config file as it looks like #133 happened in January and February 2020 but Nextcloud 20.0 (which requires this extra line) came out in October 2020.

    Adding that missing line results in the LDAP integration working again.

    image

    I'll fire up a PR to get this resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions