You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of problem:
When Content Synchronization plugin enabled, passing malformed cookie to
ldapsearch makes DS crash.
How reproducible:
always
Steps to Reproduce:
make a fresh install of DS
enable Content Synchronization plugin and Retro Changelog plugin, restart
server
run ldapsearch with malformed cookie
ldapsearch -h localhost:389 -D "cn=Directory Manager" -w Secret123 -LLL -b
dc=example,dc=com -E sync=ro/"#"
Actual results:
Server crashes
ldapsearch -h localhost:389 -D "cn=Directory Manager" -w Secret123 -LLL -b
dc=example,dc=com -E sync=ro/"#"
ldap_result: Can't contact LDAP server (-1)
Expected results:
Server should not crash and report that cookie is invalid, like in this
example:
ldapsearch -h localhost:389 -D "cn=Directory Manager" -w Secret123 -LLL -b
dc=example,dc=com -E sync=ro/"##"
Content Sync Refresh Required (4096)
Additional information: Invalid session cookie
The text was updated successfully, but these errors were encountered:
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47939
Description of problem:
When Content Synchronization plugin enabled, passing malformed cookie to
ldapsearch makes DS crash.
How reproducible:
always
Steps to Reproduce:
server
ldapsearch -h localhost:389 -D "cn=Directory Manager" -w Secret123 -LLL -b
dc=example,dc=com -E sync=ro/"#"
Actual results:
Server crashes
ldapsearch -h localhost:389 -D "cn=Directory Manager" -w Secret123 -LLL -b
dc=example,dc=com -E sync=ro/"#"
ldap_result: Can't contact LDAP server (-1)
Expected results:
Server should not crash and report that cookie is invalid, like in this
example:
ldapsearch -h localhost:389 -D "cn=Directory Manager" -w Secret123 -LLL -b
dc=example,dc=com -E sync=ro/"##"
Content Sync Refresh Required (4096)
Additional information: Invalid session cookie
The text was updated successfully, but these errors were encountered: