https://answers.axonivy.com/questions/3544/fast-ldap-user-lookup-at-runtime<p>In my project I read users at runtime via Ivy API: SecurityContext.findUser("theUser");</p> <p>This works reasonably well in my company environment. But if I deploy the project the the productive engine (to the cloud) this user lookups can take up to 2 minutes. At least if I search for a not existing user? How can I speed it up? The security system here is configured to use an LDAP. Shouldn't this be a fast protocol?</p>enWed, 14 Nov 2018 09:51:22 -0500https://answers.axonivy.com/questions/3544/fast-ldap-user-lookup-at-runtime/3546<p><strong>Before 7.2:</strong></p> <p>You can configure additional properties of an security system not that ease, see:</p> <p><a href="https://answers.axonivy.com/questions/893/how-can-i-specify-additional-properties-attributes-for-an-external-security-system">How can I specify additional properties/attributes for an External Security System?</a></p>Christian StrebelWed, 14 Nov 2018 09:51:22 -0500https://answers.axonivy.com/questions/3544/fast-ldap-user-lookup-at-runtime/3546https://answers.axonivy.com/questions/3544/fast-ldap-user-lookup-at-runtime/3545<p><strong>7.2 and later:</strong></p> <p>The solution is to use our cached user lookup: <code>SecurityContext.findUserWithoutLookup("theUser")</code> As the users are synchronized once a day into our cache table, this should be sufficient for most use cases.</p> <p>An additional improvement for cloud access to a company LDAP is to disable refereal following: <code>"java.naming.referral": ignore</code></p> <p>With this setting you speed up the lookup for not existing names as following referalls (browsing attached ADs) could take ages if you come from a different network.</p> <p>Such a config in 7.2 could look as follows <img alt="alt text" src="https://answers.axonivy.com/upfiles/ivyYaml_referral-ignore.png"></p>Reguel WermelingerWed, 14 Nov 2018 03:10:36 -0500https://answers.axonivy.com/questions/3544/fast-ldap-user-lookup-at-runtime/3545