<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">Negib,</div>
<div class=""><br class="">
</div>
<div class="">You might want to check with the LDAP directory operator, yeah. As mentioned, it's really hard for us to tell you from afar what these settings “should” be.</div>
<div class=""><br class="">
</div>
<div class="">Another possible challenge is that the default configuration with .properties assumes that you’re using one LDAP directory. A legacy JAAS configuration file would not have those strings embedded in it, so it might appear to behave differently
because it’s not inheriting the same configuration.</div>
<div class=""><br class="">
</div>
<div class="">If the directory you’re using to authenticate users is different from the directory that holds user attributes, or you need to cascade through authentication providers, you’ll at least need to understand how the different pieces are all wired
up, and you may find JAAS to be the easier short run option because of its notion of “sufficient”. Depends on your use cases.</div>
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class="">Nate.</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class=""><span style="font-family: 'Times New Roman', Times, serif; font-size: 14pt; background-color: rgb(255, 255, 255);" class="">Shib IdP works fine when I use JAAS authentication without baseDN. I want to stick with Ldap authentication. I don't have
access to LDAP log to trace the problem. I also don't want to use JAAS authentication permanently. With my Local OpenLdap the Shib IdP works fine using local Ldap configuration. I think I have to deal with the guys who are handling remote Ldap.</span></div>
</blockquote>
</div>
</body>
</html>