-
Notifications
You must be signed in to change notification settings - Fork 364
add more ldap results, ldap result from type uint8 to type uint16 #160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
smth wrong with golint in 1.6? "/bin/sh: 1: golint: not found" |
error.go
Outdated
LDAPResultAssertionFailed = 122 | ||
LDAPResultAuthorizationDenied = 123 | ||
LDAPResultSyncRefreshRequired = 4096 | ||
LDAPResultNoOperation = 16654 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the draft-zeilenga-ldap-noop draft does not specify a value for the noOperation result code... seems odd to embed a value some implementations just picked into this library
removed nooperation, still don't get why pipeline 1.6 failes |
fixed in #161 |
maybe it's better to use uint32 cos winapi uses ulong (8 bytes) for result "WINLDAPAPI ULONG LDAPAPI ldap_simple_bindW( LDAP *ld, PWCHAR dn, PWCHAR passwd );" ? |
The ldap spec says values over ~16000 aren't allowed, so uint16 is sufficient |
@liggitt any objections merging this to master? |
I hadn't swept the new codes/messages yet. Once someone does that, no objections to merging |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
More result codes taken from https://ldap.com/ldap-result-code-reference/
Result type uint8 to uint16 as the actual values exceeds uint8