[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Garbled objectClass
- To: Saša-Stjepan Bakša <ssbaksa@gmail.com>, "openldap-technical@openldap.org" <openldap-technical@openldap.org>, "Quanah Gibson-Mount" <quanah@symas.com>
- Subject: Re: Garbled objectClass
- From: Francis Swasey <Francis.Swasey@uvm.edu>
- Date: Thu, 24 Oct 2019 15:48:18 +0000
- Accept-language: en-US
- Content-language: en-US
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uvm.edu; s=s3-t1; t=1571932098; x=1572450498; bh=Pac87OHu39f2lPjHlZ+BVo8TFIWfglmM3IQi7yACQ+s=; h=From:To:Subject:Date:References:In-Reply-To:From; b=uqjMf15ZFk0zU5K6WKo57e89F50ncGBEkHakOdCET7Lmfn0rLZJ/i7PZGB/H6jH79 9F9jf3DW0fjLlKWZsZfMfwIK2w5ZSehIf5wPCJj0M/P1s+VA2hALHrPz0ojT8N5z1j pCRN0l4yITpSRMJZM16/jAxOc7shssnZYbEF1nUg=
- In-reply-to: <CEE2E1726699F38A3F4B2536@[192.168.1.144]>
- References: <CANk+c=2QFqT8uNdJDTdv_A_1j-r4H5+w3k+j1XdVhX9iZ3SVXA@mail.gmail.com>, <CEE2E1726699F38A3F4B2536@[192.168.1.144]>
- Thread-index: AQHVibqKuzs2Cx2buUuE9M75deKHY6doqDEAgAFJE8Q=
- Thread-topic: Garbled objectClass
It appears to me to be the mdash in the 'Common package description [mdash] service parameters defined by MNO' string...
________________________________________
From: openldap-technical <openldap-technical-bounces@openldap.org> on behalf of Quanah Gibson-Mount <quanah@symas.com>
Sent: Wednesday, October 23, 2019 12:09:50 PM
To: Saša-Stjepan Bakša; openldap-technical@openldap.org
Subject: Re: Garbled objectClass
--On Wednesday, October 23, 2019 5:52 PM +0200 Saša-Stjepan Bakša
<ssbaksa@gmail.com> wrote:
>
>
> Is there any good reason that I see one of my custom objectClass garbled
> like this below. It happens when I am reading content from file. From GUI
> tool it looks as it should.
This is not garbled, it's base 64 encoded. This generally occurs when a
space or tab character is left at the end of an attribute value or there is
some type of unprintable (unicode often) character contained within the
value.
Decoding it generates:
{6}( 1.3.6.1.4.1.35269.3.245.2.7 NAME 'pcrfPackage' DESC 'Common package
description – service parameters defined by MNO' SUP top STRUCTURAL MUST
( pcrfPackageTitle $ packageLifetimeType ) MAY ( packageActivationDate $
packageExpiryDate $ packageCycle $ totalMaximumVolume $ totalMaximumTime $
monitoringKey $ totalMaximumAmount $ cycleMultiplier ) )
Nothing jumps out at me here as to why it's being encoded, but hopefully
that gives you enough clues to start from.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>