Change Details

Some customers have the problem that the NameUserPrincipal we query over GetUserNameEx does not match the real email address of the user. We are currently using GetUserNameEx to avoid a full LDAP / AD Search of properties but that would be the better solution. In Powershell it could be queried like this: $([adsisearcher]"(samaccountname=$env:USERNAME)").FindOne().Properties.mail We could of course do such a search using LDAP API ourself and if we find such a property prefer this over the GetUserNameEx value. This would be more accurate in most places.

Some customers have the problem that the NameUserPrincipal we query over GetUserNameEx does not match the real email address of the user. The display name does not always give the desired result for the name, either. Since dirmngr has gained additional functions to query AD, it should not be necessary any more to use powershell commands in Kleopatra. We want to allow to configure the name an email in the "New OpenPGP Keypair" dialog via the Kleopatra registry settings EMAIL and NAME using data read from AD, environment variables, registry or local settings. This could look kind of like this: NAME={{AD.FirstName}} {{AD.Initials}} {{AD.LastName}} NAME={{ENV.USER_NAME}} NAME={{REG.LASTNAME}}, {{REG.FIRSTNAME}} ({{REG.DEPARTMENT}}) NAME={{LOCAL.DISPLAY_NAME}} Additionally we might want to change the values used for NAME_prefill and EMAIL_prefill.

Some customers have the problem that the NameUserPrincipal we query over GetUserNameEx does not match the real email address of the user. We are currently using GetUserNameEx to avoid a full LDAP / AD Search of properties but that would beThe display name does not always give the desired result for the better solutionname, either. In Powershell it could be queried like this:Since dirmngr has gained additional functions to query AD, it should not be necessary any more to use powershell commands in Kleopatra. We want to allow to configure the name an email in the "New OpenPGP Keypair" dialog via the Kleopatra registry settings EMAIL and NAME using data read from AD, environment variables, registry or local settings. This could look kind of like this: NAME={{AD.FirstName}} {{AD.Initials}} {{AD.LastName}} NAME={{ENV.USER_NAME}} $([adsisearcher]"(samaccountname=$env:USERNAME)").FindOne().Properties.mailNAME={{REG.LASTNAME}}, {{REG.FIRSTNAME}} ({{REG.DEPARTMENT}}) NAME={{LOCAL.DISPLAY_NAME}} We could of course do such a search using LDAP API ourself and if we find such a property prefer this over the GetUserNameEx value. This would be more accurate in most places.Additionally we might want to change the values used for NAME_prefill and EMAIL_prefill.