[SERVER-11242] Invalid error message or error check Created: 17/Oct/13  Updated: 10/Dec/14  Resolved: 17/Oct/13

Status: Closed
Project: Core Server
Component/s: Security
Affects Version/s: 2.5.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Sridhar Nanjundeswaran Assignee: Andreas Nilsson
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7 Enterprise Build on 2008 R2
Git hash:
mongo - 1ea7e56cb2b8653d4b0453f04728033df34be9e1
enterprise - d919ef07f817832732d2a0a2ec68251bc161193a


Operating System: ALL
Steps To Reproduce:
  • Start mongod with sslOnNormalPorts, PEM file and sslWeakCertificateValidation
    using config file
    dbpath=d:\data\db
    sslOnNormalPorts=true
    sslPEMKeyFile=c:\Users\qa377\Downloads\pems\server.pem
    sslWeakCertificateValidation=true
Participants:

 Description   

c:\Program Files\MongoDB 2.5.2 Enterprise\bin>mongod.exe --config config.conf
Error storing command line: BadValue need sslCAFile with sslWeakCertificateValid
ation

sslWeakCert doc on help is
--sslWeakCertificateValidation allow client to connect without presenting a
certificate

Hence specifying sslWeakCertificateValidation should not require sslCAFile



 Comments   
Comment by Andreas Nilsson [ 17/Oct/13 ]

It does not make sense to provide the sslWeakCertificateValidation flag unless a CA file is specified since there is nothing to be validated against.

Generated at Thu Feb 08 03:25:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.