The crush keystore won't help, its only the JVM's general keystore that is
used.

When testing, its using the local machine's keystore. When actually
operating on the server, its using its keystore there. So you need to
import it into both JVM's keystores.

Thanks,
Ben

On Thu, Jul 9, 2009 at 12:20 PM, azathoth2k64 <azathoth2k64@...>wrote:

>
>
> I imported them into the keystore that CrushFTP is using for SSL (specified
> in prefs.XML). I just imported them into the cacerts file in
> /usr/local/jre1.6.0_14/lib/security and am still seeing the same error. I am
> running this headless so the management is running on a Windows box. When
> doing the test, is the management client using the servers keystore or one
> on the local PC? Is there a way to tell which keystore it is using?
>
> Thanks,
>
> Keith
>
> --- In crushftp3support@yahoogroups.com<crushftp3support%40yahoogroups.com>,
> Ben Spink <ben@...> wrote:
> >
> > Exactly which keystores did you import the certs into?
> >
> > Are you certain its the keystore your JVM is using? The LDAPS:// is using
> > the default JVM keystore.
> >
> > Let me know,
> > Ben
> >
> > On Thu, Jul 9, 2009 at 9:49 AM, azathoth2k64 <azathoth2k64@...> wrote:
> >
> > >
> > >
> > > I am trying to get LDAPS working with our AD environment but am getting
> the
> > > error that "no trusted certificate found". I have imported the
> certificates
> > > for the AD servers into the java keystore and flagged them as trusted.
> We
> > > have other applications using LDAPS to these servers so I know that is
> > > working ok. I also have imported the certs into the JXplorer LDAP
> browser
> > > and they work fine.
> > >
> > > Thanks,
> > >
> > > Keith
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>


[Non-text portions of this message have been removed]