[
https://issues.apache.org/jira/browse/GUACAMOLE-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sbcbus updated GUACAMOLE-1885:
------------------------------
Description:
We as a group have run into the max groups of 1000 via default Active Directory
settings (via
https://docs.libraesva.com/knowledgebase/ldap-query-returns-only-1000-entries-and-ldap-sync-return-error-sizelimit-exceeded/
), despite having filters as much as has been easily feasible. Despite the
ldap-max-search-results Guacamole setting, we still are reliant on the LDAP
server restrictions as well.
Not everyone can or will get permission to adjust the default paging at an LDAP
level, so I would love to see paging support used in Guacamole as it will still
retrieve all results and is already supported by Apache LDAP.
https://nightlies.apache.org/directory/api/2.0.1/apidocs/org/apache/directory/api/ldap/model/message/controls/PagedResults.html
was:
We as a group have run into the max groups of 1000 via default Active Directory
settings (via
https://docs.libraesva.com/knowledgebase/ldap-query-returns-only-1000-entries-and-ldap-sync-return-error-sizelimit-exceeded/
), despite having filters as much as has been easily feasible. Despite the
ldap-max-search-results Guacamole setting, we still are reliant on the LDAP
server restrictions as well.
Not everyone can or will get permission to adjust the default paging at an LDAP
level, so I would love to see paging support used in Guacamole as it will still
retrieve all results and is already supported by Apache LDAP. I believe the
link below has an example.
https://stackoverflow.com/questions/17963975/apache-directory-ldap-paged-searches
> Add result paging support to LDAP auth extension
> ------------------------------------------------
>
> Key: GUACAMOLE-1885
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1885
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-auth-ldap
> Affects Versions: 1.5.3
> Reporter: sbcbus
> Priority: Minor
>
> We as a group have run into the max groups of 1000 via default Active
> Directory settings (via
> https://docs.libraesva.com/knowledgebase/ldap-query-returns-only-1000-entries-and-ldap-sync-return-error-sizelimit-exceeded/
> ), despite having filters as much as has been easily feasible. Despite the
> ldap-max-search-results Guacamole setting, we still are reliant on the LDAP
> server restrictions as well.
> Not everyone can or will get permission to adjust the default paging at an
> LDAP level, so I would love to see paging support used in Guacamole as it
> will still retrieve all results and is already supported by Apache LDAP.
> https://nightlies.apache.org/directory/api/2.0.1/apidocs/org/apache/directory/api/ldap/model/message/controls/PagedResults.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
