Description
mongo --authenticationDatabase admin -u MrAt -p @
|
MongoDB shell version: 3.3.9
|
connecting to: 127.0.0.1:27017/test |
MongoDB server version: 3.2.6
|
WARNING: shell and server versions do not match |
...
|
Cool.
mongo mongodb://MrAt:@@localhost/admin |
FailedToParse: Bad digit "@" while parsing @@localhost |
...
|
Yeah, fair enough.
mongo mongodb://MrAt:%40@localhost/admin |
MongoDB shell version: 3.3.9
|
connecting to: mongodb://MrAt:%40@localhost/admin |
2016-07-14T16:32:13.168+1000 E QUERY [thread1] Error: Authentication failed. :
|
connect@src/mongo/shell/mongo.js:221:14 |
@(connect):1:6
|
|
|
exception: connect failed
|
Poor MrAt.
mongo mongodb://MrPercent:%@localhost/admin |
MongoDB shell version: 3.3.9
|
connecting to: mongodb://MrPercent:%@localhost/admin |
MongoDB server version: 3.2.6
|
WARNING: shell and server versions do not match |
16:29:32@admin>^C
|
bye
|
MrPercent is a happy camper. Although he shouldn't be.
According to the specification this is the wrong way around. The escaped passwords should work, and the unescaped versions should fail.
URL option needs to support escape sequences.
Attachments
Issue Links
- is duplicated by
-
SERVER-27997 mongo connection URI cannot connect when there's "@" character in password
-
- Closed
-
- is related to
-
DOCS-8333 Escape "%", "@", ":", and "/" in username/password connection strings
-
- Closed
-