Issue with ldapjs and string base64 format
I have a LDAP server and the users have a property which is a jpeg photo in base64 format.
When I search for the user, this specific attribute comes with a weird string format:
,��1�3�>��F��ԯ�]KW�t�.<I����zu�+�s�9[Hd������(��4
It seems that there's an encoding issue or something.
Do you know what can I do in order to convert to base64?
I am using nodejs and ldapjs client for connecting to the LDAP server.
Thanks
encoding ldap base64 openldap ldapjs
add a comment |
I have a LDAP server and the users have a property which is a jpeg photo in base64 format.
When I search for the user, this specific attribute comes with a weird string format:
,��1�3�>��F��ԯ�]KW�t�.<I����zu�+�s�9[Hd������(��4
It seems that there's an encoding issue or something.
Do you know what can I do in order to convert to base64?
I am using nodejs and ldapjs client for connecting to the LDAP server.
Thanks
encoding ldap base64 openldap ldapjs
add a comment |
I have a LDAP server and the users have a property which is a jpeg photo in base64 format.
When I search for the user, this specific attribute comes with a weird string format:
,��1�3�>��F��ԯ�]KW�t�.<I����zu�+�s�9[Hd������(��4
It seems that there's an encoding issue or something.
Do you know what can I do in order to convert to base64?
I am using nodejs and ldapjs client for connecting to the LDAP server.
Thanks
encoding ldap base64 openldap ldapjs
I have a LDAP server and the users have a property which is a jpeg photo in base64 format.
When I search for the user, this specific attribute comes with a weird string format:
,��1�3�>��F��ԯ�]KW�t�.<I����zu�+�s�9[Hd������(��4
It seems that there's an encoding issue or something.
Do you know what can I do in order to convert to base64?
I am using nodejs and ldapjs client for connecting to the LDAP server.
Thanks
encoding ldap base64 openldap ldapjs
encoding ldap base64 openldap ldapjs
asked Nov 14 '18 at 23:22
jprivillasojprivillaso
396412
396412
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I had a similar issue, and an Issue on the ldapjs github page provided the solution. Essentially you're getting the value converted to a string (which, as you see is a bunch of useless rubbish) and need to get the unconverted buffer for binary properties. The second post in the issue provides code to accomplish this.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53310257%2fissue-with-ldapjs-and-string-base64-format%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had a similar issue, and an Issue on the ldapjs github page provided the solution. Essentially you're getting the value converted to a string (which, as you see is a bunch of useless rubbish) and need to get the unconverted buffer for binary properties. The second post in the issue provides code to accomplish this.
add a comment |
I had a similar issue, and an Issue on the ldapjs github page provided the solution. Essentially you're getting the value converted to a string (which, as you see is a bunch of useless rubbish) and need to get the unconverted buffer for binary properties. The second post in the issue provides code to accomplish this.
add a comment |
I had a similar issue, and an Issue on the ldapjs github page provided the solution. Essentially you're getting the value converted to a string (which, as you see is a bunch of useless rubbish) and need to get the unconverted buffer for binary properties. The second post in the issue provides code to accomplish this.
I had a similar issue, and an Issue on the ldapjs github page provided the solution. Essentially you're getting the value converted to a string (which, as you see is a bunch of useless rubbish) and need to get the unconverted buffer for binary properties. The second post in the issue provides code to accomplish this.
answered Nov 17 '18 at 15:11
LisaJLisaJ
770313
770313
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53310257%2fissue-with-ldapjs-and-string-base64-format%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown