Remove prefix net from Import Npriting

[ThiagoCN]

Hello Guys


I trying to create one import but all the time i import the user i got this message "as Generic LDAP and with main directory prefix net"

Because of that the domain account in nPrinting import get like this : net/Domain/UserID

There is any way i can remove this "NET" during the import ?

[Ruggero_Piccoli]

Hi,

Where do you see the message during users LDAP import? Can you post a screenshot?

Best Regards,

Ruggero

[ThiagoCN]

Hello @Ruggero_Piccoli 

I will Hiding  the LDAP link, but keep the rest i have this

and the user in import is like this

Hiding the Domain  and UserId

[Ruggero_Piccoli]

Hi,

Thanks for the screenshots. The first is related to logs and you cannot change the logs structure but they are for administrators. About the second one, is the imported domain user correct? Can an imported user login correctly by pressing Windows Login button?

Best Regards,

Ruggero

[ThiagoCN]

Hi @Ruggero_Piccoli  the only issue is because it's came with this new 

let use example 

net\Pluto\ThiagoCN

Net = > Generic Ldap Domain
Pluto = > My user Domain
Thiago CN =  my user

Because of this net in front is not working what I expect is:
Pluto\ThiagoCN

because if this net nPrinting say is not a valid domain

[Ruggero_Piccoli]

Hi,

I suspect there is something wrong in the LDAP user import configuration. Parameters are described in https://help.qlik.com/en-US/nprinting/May2021/Content/NPrinting/DeployingQVNprinting/Import-Users-Fi... and I suggest you to check with the help of your LDAP administrator to find the correct configuration that can be customized thanks to the LDAP features. Another way could be use a third party LDAP visualization tool to obtain the correct paramenters.

Best Regards,

Ruggero

[Frank_S]

Further to @ruggero_piccolo comment, a commonly used LDAP tool is ldap admin that will expose accurately formed Ldap paths.

You may use the link to this tool at your discretion.

• http://www.ldapadmin.org/screenshots/index.html

Kind regards...

[ThiagoCN]

Hi @Frank_S and @Ruggero_Piccoli 
The problem is i not allow to install this kind of application there a big security here I have spoke with LDAP team and they give me this answer:

"Hi, LDAP does not store the information that way, it seems to be problem with your LDAP library used in the code, you need to check documentation of your library or just replace that in the code if it is always appended, AD has two main naming convention, DN like this CN=M12345_DA,OU=Functional,OU=Tier0,OU=PAWs,OU=AppServices,DC=gbl,DC=ad,DC=serverhere,DC=net or canonical name like this: gbl.ad.server.net/AppServices/PAWs/Tier0/Functional/M12345_DA"


I not good in LDAP stuffs I do not get it what he is saying, but basically he is saying : " it not LDAP configure issue
is with the tool you are using "

[ThiagoCN]

Ok they give a new update 

unfortunately, this causes the problem for multi-domain environment, as in Universal groups you can have members from other domains as well, you need to change the security model for this app or ask vendor how you should handle multi-domain environment

if i know correctly i have to create one import for each Domain i have?

[Ruggero_Piccoli · Accepted solution]

Hi,

In a single Import Task you can add multiple LDAP sources also together with Excel sources. So you can create 2 Import tasks or one with two sources.

Best Regards,

Ruggero