Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-4488

Not abiding by Crowd's Allow all to authenticate - False

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 1.3.1
    • None

      Not sure if this is HipChat or Crowd, however I had a Crowd internal directory with a bunch of users, and a group within it with only 2 users

      I've setup a Hipchat application against the directory, Allow all to authenticate is set to false, and under Groups, only the group with the two users set with access.

      When I sync the directory, I get 252 users synced, not just the 2 from the group I want to give permission to.

      I've removed and re-added the directory and got the 252 users again

            [CWD-4488] Not abiding by Crowd's Allow all to authenticate - False

            You can use Crowd to filter the users coming from AD, either by setting up a user filter in the Connector directory in Crowd, or by using a Delegated Auth directory in Crowd to managing the users in Crowd, depending on your needs.

            Diego Berrueta added a comment - You can use Crowd to filter the users coming from AD, either by setting up a user filter in the Connector directory in Crowd, or by using a Delegated Auth directory in Crowd to managing the users in Crowd, depending on your needs.

            So for an application like HipChat that has an upper limit of 5000 users, where we're trying to use "enterprise" ready tools, where we have 60,000 staff globally coming in via AD plus hundreds (growing to thousands) of other accounts (clients and contractors) coming in via our crowd third party database, we're meant to do what exactly?

            Craig Castle-Mead added a comment - So for an application like HipChat that has an upper limit of 5000 users, where we're trying to use "enterprise" ready tools, where we have 60,000 staff globally coming in via AD plus hundreds (growing to thousands) of other accounts (clients and contractors) coming in via our crowd third party database, we're meant to do what exactly?

            The implications towards the licensing have been noted before, see CWD-137.

            At the moment, Remote Crowd directories do not support user filtering based on group memberships.

            Diego Berrueta added a comment - The implications towards the licensing have been noted before, see CWD-137. At the moment, Remote Crowd directories do not support user filtering based on group memberships.

            Diego - thanks for the reply. While CWD-1348 seems to cover the situation, it's throwing licensed user count for HipChat out. We want 2 of our users in this directory to be able to use the application, however all 252 are showing against the user count, and then in the user listing interface.

            Craig Castle-Mead added a comment - Diego - thanks for the reply. While CWD-1348 seems to cover the situation, it's throwing licensed user count for HipChat out. We want 2 of our users in this directory to be able to use the application, however all 252 are showing against the user count, and then in the user listing interface.

            Hello craig.castlemead. I think this issue duplicates CWD-1348. Please add a comment if that's not the case.

            Diego Berrueta added a comment - Hello craig.castlemead . I think this issue duplicates CWD-1348 . Please add a comment if that's not the case.

              Unassigned Unassigned
              1af51783067a Craig Castle-Mead
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: