<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:59:41 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[CXX-594] Auth against MongoDB 3 not working</title>
                <link>https://jira.mongodb.org/browse/CXX-594</link>
                <project id="11980" key="CXX">C++ Driver</project>
                    <description>&lt;p&gt;According to the compatibility matrix at &lt;a href=&quot;http://docs.mongodb.org/ecosystem/drivers/cpp/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://docs.mongodb.org/ecosystem/drivers/cpp/&lt;/a&gt; the compat driver should be fully compatible to mongodb 3, but we haven&apos;t been able to authenticate using &lt;br/&gt;
bool auth(const string &amp;amp;dbname, const string &amp;amp;username, const string &amp;amp;pwd, string&amp;amp; errmsg, bool digestPassword = true);&lt;br/&gt;
against a newly created mongo 4  replicaset&lt;/p&gt;

&lt;p&gt;This might be caused by tha default authentication change - but I have not been able to find a way to define MONGODB-CR users ?&lt;/p&gt;


</description>
                <environment></environment>
        <key id="202968">CXX-594</key>
            <summary>Auth against MongoDB 3 not working</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="andrew.morrow@mongodb.com">Andrew Morrow</assignee>
                                    <reporter username="christian.wyss@gfk.com">Christian Wyss</reporter>
                        <labels>
                    </labels>
                <created>Fri, 8 May 2015 16:43:58 +0000</created>
                <updated>Thu, 21 May 2015 12:41:55 +0000</updated>
                            <resolved>Thu, 21 May 2015 12:41:55 +0000</resolved>
                                    <version>legacy-0.0-26compat-2.6.9</version>
                                                                        <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="920072" author="christian.wyss@gfk.com" created="Thu, 21 May 2015 07:05:34 +0000"  >&lt;p&gt;No, thank you - go ahead and close&lt;/p&gt;</comment>
                            <comment id="919136" author="acm" created="Wed, 20 May 2015 15:09:33 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=christian.wyss%40gfk.com&quot; class=&quot;user-hover&quot; rel=&quot;christian.wyss@gfk.com&quot;&gt;christian.wyss@gfk.com&lt;/a&gt; - Is there anything else we can help you with in this ticket? If not, I&apos;d like to close it.&lt;/p&gt;</comment>
                            <comment id="910045" author="christian.wyss@gfk.com" created="Mon, 11 May 2015 15:51:24 +0000"  >&lt;p&gt;Ok - done. Thank you&lt;/p&gt;</comment>
                            <comment id="910033" author="acm" created="Mon, 11 May 2015 15:39:35 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=christian.wyss%40gfk.com&quot; class=&quot;user-hover&quot; rel=&quot;christian.wyss@gfk.com&quot;&gt;christian.wyss@gfk.com&lt;/a&gt; - &lt;/p&gt;

&lt;p&gt;Apologies, you are correct. Still, I recommend you file a SERVER project enhancement ticket if you wish to request the ability to explicitly create MONGODB-CR users in 3.0.&lt;/p&gt;</comment>
                            <comment id="910012" author="christian.wyss@gfk.com" created="Mon, 11 May 2015 15:24:56 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=acm&quot; class=&quot;user-hover&quot; rel=&quot;acm&quot;&gt;acm&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I wasn&apos;t thinking about a downgrade-machanism but rather about a way to NOT have to downgrade the full server but only create the CR-Credentials for specific users and leave the default as it is.&lt;/p&gt;</comment>
                            <comment id="909982" author="acm" created="Mon, 11 May 2015 15:04:16 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=christian.wyss%40gfk.com&quot; class=&quot;user-hover&quot; rel=&quot;christian.wyss@gfk.com&quot;&gt;christian.wyss@gfk.com&lt;/a&gt; - &lt;/p&gt;

&lt;p&gt;The decision to de-support MONGODB-CR in MongoDB 3.0 by default was deliberate. If you are interested, you can always file a SERVER enhancement ticket requesting a supported mechanism for downgrading, but I wouldn&apos;t be optimistic.&lt;/p&gt;


</comment>
                            <comment id="909955" author="christian.wyss@gfk.com" created="Mon, 11 May 2015 14:43:40 +0000"  >&lt;p&gt;Hi Andrew Morrow&lt;/p&gt;

&lt;p&gt;Thanks for the quick response.&lt;/p&gt;

&lt;p&gt;As said: some means to create MONGODB-CR users in Mongo3 without having to change the default behaviour would be nice - i.e. createUser( ... &lt;/p&gt;
{method : &quot;MONGODB-CR&quot;}
&lt;p&gt;) or something alike.&lt;/p&gt;

&lt;p&gt;Beside this there&apos;s not much, I guess.&lt;/p&gt;</comment>
                            <comment id="909945" author="acm" created="Mon, 11 May 2015 14:38:05 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=christian.wyss%40gfk.com&quot; class=&quot;user-hover&quot; rel=&quot;christian.wyss@gfk.com&quot;&gt;christian.wyss@gfk.com&lt;/a&gt; -&lt;/p&gt;

&lt;p&gt;Thanks for filing this. I agree that the compatibility matrix doesn&apos;t capture this aspect of using the 26compat series driver with the 3.0 server, and it probably should. As you have noted, the underlying issue is that the default auth schema for a new installation of MongoDB 3.0 only does SCRAM, which the 26compat driver series will never support (the legacy driver 1.0.0+ does). If you must use the 26compat driver with the 3.0 server, you will need to use MONGODB-CR. I believe that downgrading the auth schema is the only means to achieve that in a non-upgrade scenario.&lt;/p&gt;

&lt;p&gt;I will get compatibility matrix updated to reflect this.&lt;/p&gt;

&lt;p&gt;In the meantime, is there anything more you would like us to do on this ticket?&lt;/p&gt;</comment>
                            <comment id="909674" author="christian.wyss@gfk.com" created="Mon, 11 May 2015 07:01:33 +0000"  >&lt;p&gt;After some more research found this Jira entry:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-17459&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://jira.mongodb.org/browse/SERVER-17459&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&amp;gt; var schema = db.system.version.findOne(&lt;/p&gt;
{&quot;_id&quot; : &quot;authSchema&quot;}
&lt;p&gt;)&lt;br/&gt;
&amp;gt; schema.currentVersion = 3&lt;br/&gt;
&amp;gt; db.system.version.save(schema)&lt;/p&gt;

&lt;p&gt;Worked&lt;/p&gt;

&lt;p&gt;It would still be interesting to have a possibility to add a &quot;MONGODB-CR-user&quot; without having to change this default!&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="203312">SERVER-18412</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="203420">DOCS-5414</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hs95zr:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>