and more in a single search tool across platforms. Read the announcement here. |
08/02/2023 12:31 PM
We have a use case to import a certificate data value stored in LDAP data store, with a base64 data type. Import into either Account or User schema via the LDAP connector is ignoring this attribute mapping and the import job is successful. There are no errors in the logs.
Is there a way to import this certificate value?
We don't need the entire certificate value but just looking for a particular key value pair from the certificate.
08/06/2023 09:06 PM
Hi @igaravi
Can you share your ImportAccountEntJSON? Right now what value is showing up at that attribute after running import?
Thanks
08/06/2023 09:22 PM
Can you share sample value and current json, You may be able to do with #CONST#
08/10/2023 11:05 AM
The account import mapping is below. I tried both string and Binary datatypes on the mapping but did not work. Not sure how to specify #CONST# on account import. The source is stored as base64 and my front end GUI LDAP browser is showing the value in either binary or text format (attached this source value in text format).
[ACCOUNTID::duid#String,
NAME::uid#String,
COMMENTS::hspdEncryptionCertificate#String,
RECONCILATION_FIELD::ACCOUNTID]