× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



We are working with a consultant to help us get EIM setup for single signon using Active Directory. Everything we do with Client Access we run as SSL. Our system name is as400adm.pct.edu when we setup the connection for Client Access. We also run Apache on this system and have it secured with a Verisign certificate. The certificate is registered as as400sec.pct.edu. We use to run the web server as as400adm.pct.edu and them added a secure site and used as400sec.pct.edu for that name. The Kerberos part of the setup for EIM appears to be working fine and testes our at qshell. We assigned our Verisign certificate to the LDAP server and EIM in DCM. Got Tivoli Directory setup to use SSL but EIM said it could not communicate with the Directory. Consultant thought it was probably due to the mismatch between the system name of as400adm.pct.edu and the certificate name of as400sec.pct.edu. We then tried to create a local CA and issue a certificate under the name as400adm.pct.edu and assign that cert to LDAP Directory and EIM but still get an error that something is wrong with the certificate chain. We have another session with the consultant this afternoon and hope to get a ticket open with IBM for the same time but wanted to ask the group if anyone has ever done EIM setup using SSL and if you might have any tips for where we might look to resolve this.

Thanks
Mike Cunningham

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.