Function requires attributes to be of type x, validate to ensure any changes will break function and to prevent further exceptions. Only output to console as it's only a developer who will generate this error.

PR-#13777

As the user provides some of the ldap attributes, validate those entries when the 'LDAP Settings' editor clicks save. Provide an error message if validation fails stating what is incorrect.

issue #13738 PR-#13777

A user object is passed to the function. Use this to derived the user details.

PR #13777

sider #issue-5810499

a user document is passed to the function. use this to derive user details

issue #13738

A blank password causes exception 'ldap3.core.exceptions.LDAPPasswordIsMandatoryError'. Validate the user input.

Issue #13738

ldap search string is user input. validate to ensure is enclosed in '()', has the '{0}' placeholder and has the same number of brackets as used in complex ldap search strings.

issue #13738

to confirm user credentials, use 'rebind' instead of re-connecting to ldap. This also enables unit testing of all functions except the connection to ldap.

issue #13738

ldap_group_field set for depreciation.

issue #13738 fixes frappe/frappe#10794

issue #13738

Validate the LDAP search filter including enclosing in '()'. Note: if a user has a complex filter that misses the last ')' it will not be added. i.e. (&(objectclass=posixgroup)(uid={0}) is invalid but will pass validation.

issue #13738

User needs to be able to conduct complex filtering. As long as the placeholder '{0}' for the username is included in the ldap search filter, the user can customize as required. searches must be enclosed in '()' i.e '(uid={0}) or '(&(objecttype=posixaccount)(uid={0}))' etc.

issue #13738 close frappe/frappe#6037

All LDAP operations should be done by ldap base dn user. This allows an administrator to lock down their directory to the user the LDAP operations are being conducted by.

issue #13738

adjusted to posixgroup as openldap groups use objectclass 'posixgroup' for both a posix group and a samba group.

issue #13738

as part of the search the login/user name is required to find the user

issue #13738

New method to search for user group membership. Replaces old logic of using an ldap users attribute memberof which is not supported by all LDAP implementations

issue #13738

Add new fields for the new group feature

issue #13738

ci: Remove test suite TestFrappeHTTPRequest

Remove tests for HTTPRequest under test_auth because Frappe
develop CI started breaking after PR merge

refactor: Request Language Resolution

ORM wrapper for SQL DDL statement

* Alias frappe.db.clear_table to use truncate
* Support for __ tables is added here

* Rename conditions kwarg to filters. Handle conditions kwarg if passed
* Re-added exc raise for no filters...to risky. Thinking of having an
  extra kwarg like `force` or something...undecided
* Added Python type hints
* Accept and pass kwargs to frappe.db.sql...Now pass any kwarg db.sql
  accepts
* Pass debug from fn def if someone is still using it as a positional
  arg :thonk:

fix: Allow navigation to the document with # in the docname

fix: multiple form tour issues

fix: `show Report` button in report view (backport #13749)

frappe orm

raw queries to frappe orm

frappe orm

to frappe orm in desk

core