<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:09:01 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>[SERVER-5479] Arbiter in authenticated replica set should allow and require login/auth for admin-only operations</title>
                <link>https://jira.mongodb.org/browse/SERVER-5479</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;Create a replica set with one primary, one secondary and one arbiter, each started with --auth and --keyFile.  Create a user in the admin database on the primary and log in with db.auth().  Admin-only commands like logRotate work on the primary.  Set db to the local database on the secondary but do not log in with db.auth().  Admin-only commands fail as they should.  Now set db to the local database on the arbiter.  Admin-only commands work without log-in.&lt;/p&gt;

&lt;p&gt;This is convenient, since you CAN&apos;T log in to the arbiter ... it has no admin database to hold the system.users collection.&lt;/p&gt;

&lt;p&gt;This is both inconsistent and a security problem.  Once connected to the arbiter, the commands &quot;use admin&quot; and &quot;db.shutdownServer()&quot; will shut down the arbiter, for example.&lt;/p&gt;

&lt;p&gt;We should add a mechanism to make the admin.system.users collection from the primary available to the arbiter and enforced by the arbiter so that if authentication is running on the replica set then the arbiter follows the same rules as the primary and secondaries.&lt;/p&gt;</description>
                <environment>Tested on Ubuntu 11.10 64-bit with 2.0.3 and today&amp;#39;s 2.1.1-pre- but probably the same on all platforms.</environment>
        <key id="35307">SERVER-5479</key>
            <summary>Arbiter in authenticated replica set should allow and require login/auth for admin-only operations</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="10038" iconUrl="https://jira.mongodb.org/images/icons/subtask.gif" description="">Backlog</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="backlog-server-security">Backlog - Security Team</assignee>
                                    <reporter username="tad">Tad Marshall</reporter>
                        <labels>
                            <label>datarepl3.2</label>
                    </labels>
                <created>Mon, 2 Apr 2012 20:00:24 +0000</created>
                <updated>Wed, 30 Aug 2023 09:29:21 +0000</updated>
                                            <version>2.0.3</version>
                    <version>2.1.0</version>
                                                    <component>Admin</component>
                    <component>Replication</component>
                    <component>Security</component>
                                        <votes>42</votes>
                                    <watches>68</watches>
                                                                                                                <comments>
                            <comment id="3611057" author="JIRAUSER1257089" created="Thu, 11 Feb 2021 08:25:41 +0000"  >&lt;p&gt;You can use this workaround.&lt;/p&gt;

&lt;p&gt;Stop the arbiter and restart in Maintenance mode (see &lt;a href=&quot;https://docs.mongodb.com/manual/tutorial/perform-maintence-on-replica-set-members/index.html)&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://docs.mongodb.com/manual/tutorial/perform-maintence-on-replica-set-members/index.html)&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Then create the Shard Local Admin User.&lt;/p&gt;

&lt;p&gt;Restart the Arbiter node in normal mode&lt;/p&gt;

&lt;p&gt;Of course, these steps should be done as part of the Mongo deployment.&lt;/p&gt;</comment>
                            <comment id="2211032" author="alistair.evans" created="Fri, 12 Apr 2019 14:26:36 +0000"  >&lt;p&gt;Hey, just wanted to add on this issue that none of the workarounds provided seem to work (on 3.4.1); in general this problem is a major pain/concern for implementation on Windows Servers.&#160;&lt;/p&gt;

&lt;p&gt;The only available option is to stop the arbiter, rename the file and then start it again. This isn&apos;t too&#160;**bad if the majority of the set is healthy at the moment of restart, but if there are issues with the set at that moment, the Primary may step down, causing errors until the arbiter is back up and the majority is restored.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;/p&gt;

&lt;p&gt;Alistair&lt;/p&gt;</comment>
                            <comment id="2039504" author="spencer.jackson@10gen.com" created="Tue, 23 Oct 2018 18:01:35 +0000"  >&lt;p&gt;Hi, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=eliad&quot; class=&quot;user-hover&quot; rel=&quot;eliad&quot;&gt;eliad&lt;/a&gt;. Because arbiters do not persist data, they don&apos;t have access to user credentials or privileges, and so cannot perform normal authentication/authorization. Changing arbiters to store cluster data would make authentication possible, but would be a significant change in behavior with operational considerations, and would require currently unscheduled development resources.&lt;/p&gt;

&lt;p&gt;Up-thread, there are some suggested workarounds which allow clients to authenticate as the &lt;tt&gt;__system&lt;/tt&gt; user, and perform administrative actions, which I hope will help until a comprehensive solution is designed and implemented.&lt;/p&gt;

&lt;p&gt;Spencer&lt;/p&gt;</comment>
                            <comment id="2038709" author="eliad" created="Tue, 23 Oct 2018 06:41:56 +0000"  >&lt;p&gt;any update? maybe on version 4.0?&lt;/p&gt;</comment>
                            <comment id="1774401" author="bgsosh@gmail.com" created="Mon, 15 Jan 2018 16:06:01 +0000"  >&lt;p&gt;And updates here?&lt;/p&gt;</comment>
                            <comment id="1574169" author="jyotman94" created="Thu, 18 May 2017 08:15:08 +0000"  >&lt;p&gt;Any update on this issue? This is a big problem.&lt;/p&gt;</comment>
                            <comment id="1279344" author="hh@dexi.io" created="Tue, 31 May 2016 09:14:04 +0000"  >&lt;p&gt;Still an issue on version 3.0.2&lt;/p&gt;</comment>
                            <comment id="706496" author="jared" created="Thu, 28 Aug 2014 08:30:41 +0000"  >&lt;p&gt;I&apos;d like to see consistent credentials across the entire cluster, including the arbiter. In versions &amp;gt;= 2.6 I&apos;m guessing this would mean replicating the &lt;tt&gt;admin.users&lt;/tt&gt; collection. For users with privileges to do things that make no sense on an arbiter, performing such operations could just fail with the errors they already get if they try to do the same things as a super user.&lt;/p&gt;

&lt;p&gt;This would be useful for remote monitoring (e.g. MMS trying to run &lt;tt&gt;serverStatus&lt;/tt&gt;) as well as remote operations like the one suggested in &lt;a href=&quot;http://docs.mongodb.org/manual/tutorial/upgrade-cluster-to-ssl/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;step 3 of the SSL upgrade&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;For each node of a cluster, use the setParameter command to update the sslMode to preferSSL. [1] With preferSSL as its net.ssl.mode, the node accepts both SSL and non-SSL incoming connections, and its connections to other servers use SSL. For example:&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;db.getSiblingDB(&apos;admin&apos;).runCommand( { setParameter: 1, sslMode: &quot;preferSSL&quot; } )&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;Upgrade all nodes of the cluster to these settings.&lt;/p&gt;

&lt;p&gt;At this point, all connections should be using SSL.&lt;/p&gt;&lt;/blockquote&gt;
</comment>
                            <comment id="706490" author="jared" created="Thu, 28 Aug 2014 08:09:23 +0000"  >&lt;p&gt;It should be noted that logging in as &lt;tt&gt;__system&lt;/tt&gt; using the key file as the password only works if your &lt;tt&gt;clusterAuthMode&lt;/tt&gt; is &lt;tt&gt;keyFile&lt;/tt&gt; (the default). If you switch to using &lt;tt&gt;x509&lt;/tt&gt; there is no more key file.&lt;/p&gt;</comment>
                            <comment id="636351" author="schwerin" created="Fri, 27 Jun 2014 14:33:27 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=brettcave&quot; class=&quot;user-hover&quot; rel=&quot;brettcave&quot;&gt;brettcave&lt;/a&gt;, you should be able to use the contents of the keyFile to authenticate against the arbiter.  Authenticate as the user &quot;__system&quot; on the &quot;local&quot; database.  To convert the contents of the keyFile into a password you can use in the shell, typically it is only necessary to strip out the whitespace characters.&lt;/p&gt;</comment>
                            <comment id="636072" author="brettcave" created="Fri, 27 Jun 2014 07:51:45 +0000"  >&lt;p&gt;Is it possible to use key-based authentication (in the same way that the RS authenticates using a key) - if that is possible, then monitoring / connections could be made using the key.&lt;/p&gt;</comment>
                            <comment id="636067" author="brettcave" created="Fri, 27 Jun 2014 07:44:11 +0000"  >&lt;p&gt;We&apos;re using MMS monitoring service, and are unable to monitor any arbiters because of this issue. &lt;/p&gt;</comment>
                            <comment id="550867" author="spencer" created="Tue, 15 Apr 2014 22:56:44 +0000"  >&lt;p&gt;To clarify, the current behavior when connecting to an arbiter with security enabled is that by default connections over localhost will be given full access (which will allow things like shutting down the arbiter), but remote connections will be denied all access.  This is due to the &lt;a href=&quot;http://docs.mongodb.org/manual/core/authentication/#localhost-exception&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;localhost exception&lt;/a&gt; and the fact that the arbiter will always believe it has no users configured (as it has no admin database).  If you disable the localhost exception (using the &lt;a href=&quot;http://docs.mongodb.org/manual/reference/parameters/#param.enableLocalhostAuthBypass&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;enableLocalhostAuthBypass&lt;/a&gt; option to setParameter), then &lt;b&gt;all&lt;/b&gt; connections will be completely denied access.  The only way to shut down the arbiter in that case would be through a signal from the operating system.&lt;/p&gt;</comment>
                            <comment id="306628" author="gchaplin" created="Fri, 5 Apr 2013 11:17:31 +0000"  >&lt;p&gt;Bump for the greater good. Still an issue on 2.4.1.&lt;br/&gt;
We should only need to perform the addUser function once on the master and the Arbiter should sync up.&lt;br/&gt;
The other problem is that you can only add users on the Arbiter after the RS has been initiated, which does become an arduous job:&lt;/p&gt;
&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;{&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;	&quot;ok&quot; : 0,&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;	&quot;errmsg&quot; : &quot;couldn&apos;t initiate : member &amp;lt;hostname:port&amp;gt; has data already, cannot initiate set.  All members except initiator must be empty.&quot;&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;}&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;</comment>
                            <comment id="108699" author="tad" created="Wed, 11 Apr 2012 14:21:31 +0000"  >&lt;p&gt;Some new information from the affected customer:&lt;br/&gt;
--------------------&lt;br/&gt;
Hi,&lt;/p&gt;

&lt;p&gt;We recently identified a bug where some authentication events were processed differently when the client was running on the same machine as the server. My testing was in an environment like this: I used different ports for the primary, secondary and arbiter, but all were running on the same machine and I connected to each of them from a mongo shell running on the same machine. This is a standard test scenario for us, but we will need to do more testing with access from different IP addresses now that we know about this issue.&lt;/p&gt;

&lt;p&gt;Can you try issuing your logRotate command from a mongo shell running on the same machine/instance as the arbiter and see if you can duplicate my result? In my test, logRotate worked.&lt;/p&gt;

&lt;p&gt;Thanks, let me know how this works!&lt;/p&gt;

&lt;p&gt;Tad&lt;br/&gt;
--------------------&lt;br/&gt;
Hi Tad,&lt;/p&gt;

&lt;p&gt;You are right, running all mongo in the same machine and different ports the logRotate works. &lt;br/&gt;
But if the primary and secondary are in different machines, the logRotate doesn&apos;t work, even if the Arbiter server and the client machine are the same.&lt;br/&gt;
--------------------&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                        <issuelink>
            <issuekey id="76533">DRIVERS-90</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="77052">PYTHON-523</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="77047">RUBY-616</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="102936">SERVER-12143</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="276284">SERVER-23443</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="93130">SERVER-11075</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="162873">SERVER-15588</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="102936">SERVER-12143</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="1760837">SERVER-57277</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="213232">DOCS-5728</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>15.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_12751" key="com.atlassian.jira.plugin.system.customfieldtypes:multiselect">
                        <customfieldname>Assigned Teams</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="25129"><![CDATA[Server Security]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10011" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Backwards Compatibility</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10011"><![CDATA[Minor Change]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_13552" key="com.go2group.jira.plugin.crm:crm_generic_field">
                        <customfieldname>Case</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[[500A000000XUWf9IAH, 500A000000UaSmfIAF, 500A000000bBlVTIA0, 5002K00000daqs2QAA, 5002K00000mrmDmQAI, 5002K00000xl2SGQAY, 5006R00001vyGvRQAU]]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 5 Apr 2013 11:17:31 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        2 years, 51 weeks, 6 days ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            2 years, 51 weeks, 6 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>alistair.evans</customfieldvalue>
            <customfieldvalue>schwerin@mongodb.com</customfieldvalue>
            <customfieldvalue>backlog-server-security</customfieldvalue>
            <customfieldvalue>brettcave</customfieldvalue>
            <customfieldvalue>eliad</customfieldvalue>
            <customfieldvalue>gchaplin</customfieldvalue>
            <customfieldvalue>hh@dexi.io</customfieldvalue>
            <customfieldvalue>jared</customfieldvalue>
            <customfieldvalue>jyotman94</customfieldvalue>
            <customfieldvalue>bgsosh@gmail.com</customfieldvalue>
            <customfieldvalue>spencer@mongodb.com</customfieldvalue>
            <customfieldvalue>spencer.jackson@mongodb.com</customfieldvalue>
            <customfieldvalue>tad</customfieldvalue>
            <customfieldvalue>wernfried.domscheit@sunrise.net</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hro7fb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|htyzpz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>4046</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrkd2n:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>