Sorry spell checker on my phone did some thing going strange it replaced CNAME with came. So in the alternative CNAME scenario the subject can match a CNAME in the DNS but that CNAME must match an A record with a matching reverse lookup record for the forward A record. You can also use /etc / hosts files to work around this on Windows it's located in C:\windows\system32\etc Sent from my BlackBerry - the most secure mobile device
This is a general SSL TLS thing. In general the host must be resolvable Via a A record in the DNS which matches both a forward and reverse lookup. Alternatively you can use a came for the forward lookup but it must map to a A record which has a matching reverse lookup record to the A record the came points to. Sent from my BlackBerry - the most secure mobile device
Hello, Is it possible to secure communication between my 389DS console on my Window7 client computer and my 389-admin server on my Centos Server ? I want to use HTTPS instead HTTP. Is there any limitation between the server's FQDN and the subject of the Centos HTTPS server certificate ? You will find below releases and versions of my main 389 components:
| ||||||||||||||
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
