Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
ubuntu 14.04. mongo 3.0.5 / wired tiger. Using server, cluster and client certificates signed by a CA.
*Location*: http://docs.mongodb.org/manual/tutorial/configure-x509-member-authentication/
*User-Agent*: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0
*Referrer*: http://docs.mongodb.org/manual/tutorial/upgrade-cluster-to-ssl/
*Screen Resolution*: 1440 x 900
*repo*: docs
*source*: tutorial/configure-x509-member-authentication
ubuntu 14.04. mongo 3.0.5 / wired tiger. Using server, cluster and client certificates signed by a CA. *Location*: http://docs.mongodb.org/manual/tutorial/configure-x509-member-authentication/ *User-Agent*: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0 *Referrer*: http://docs.mongodb.org/manual/tutorial/upgrade-cluster-to-ssl/ *Screen Resolution*: 1440 x 900 *repo*: docs *source*: tutorial/configure-x509-member-authentication
-
0.25
Description
I couldn't add a member on a new mongo server with x509 cluster authentication enabled until I made the O, OU (and DC) attributes of the certificates match those of the server KEYPemFile. When they differ, the server to be added returns a 'could not find user' error.
The description says that the O, OU and DC attributes need to match within the cluster certificates, but doesn't mention that they should match the server certificates also.