<!-- 
RSS generated by JIRA (8.1.3#801003-sha1:6b6f07cffadda9a0d6efe24639daed8ce94dcdd6) at Sat Feb 10 05:51:21 GMT 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>Rivet Logic Corporation JIRA </title>
    <link>https://issues.rivetlogic.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.1.3</version>
        <build-number>801003</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[CMA-21] Need a method that returns the Alfresco username given a ticket</title>
                <link>https://issues.rivetlogic.com/browse/CMA-21</link>
                <project id="10015" key="CMA">Remote Alfresco API rivet</project>
                    <description>For JPMC we need to have the ability to get the Alfresco username when a user logs in. A ticket is not enough.&lt;br/&gt;
&lt;br/&gt;
This is needed since they have written a Janus authentication component that is chained and sets the Alfresco user to an SID which is provided by a successful authentication into Janus. This SID is different from the username that we used to login in the CMA client app. This SID is equal to the Alfresco username.&lt;br/&gt;
&lt;br/&gt;
Since the client app in this case is totally unaware of the Alfresco username we have no way of getting our hands on the user&amp;#39;s profile from Alfresco. That&amp;#39;s why we need to have a way to get the username after authentication.&lt;br/&gt;
&lt;br/&gt;
One suggestion would be to overload CMA&amp;#39;s authenticate() method to return the username somehow. This will allow us not to have to make two CMA calls instead of one.&lt;br/&gt;
&lt;br/&gt;
This new feature is critical for the JPMC project so please give it a high priority.&lt;br/&gt;
&lt;br/&gt;
Thanks a mil,&lt;br/&gt;
&lt;br/&gt;
-Alaaeldin</description>
                <environment></environment>
        <key id="11074">CMA-21</key>
            <summary>Need a method that returns the Alfresco username given a ticket</summary>
                <type id="2" iconUrl="https://issues.rivetlogic.com/secure/viewavatar?size=xsmall&amp;avatarId=11091&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="1" iconUrl="https://issues.rivetlogic.com/images/icons/priorities/blocker.svg">Blocker</priority>
                        <status id="6" iconUrl="https://issues.rivetlogic.com/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="green"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="aelnattar">Al El-Nattar</assignee>
                                    <reporter username="aelnattar">Al El-Nattar</reporter>
                        <labels>
                    </labels>
                <created>Tue, 1 Jul 2008 08:23:36 -0400</created>
                <updated>Fri, 21 May 2010 12:49:35 -0400</updated>
                            <resolved>Wed, 2 Jul 2008 08:17:10 -0400</resolved>
                                                    <fixVersion>1.2.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>0</watches>
                                                                <comments>
                            <comment id="11301" author="sumer" created="Tue, 1 Jul 2008 08:59:03 -0400"  >Let&amp;#39;s embed the user name in the ticket if possible. Also, if we can have a function to return the uname given a ticket (straight from Alfie), then we can implement that as well.&lt;br/&gt;
&lt;br/&gt;
Thanks.</comment>
                            <comment id="11312" author="hlim" created="Wed, 2 Jul 2008 08:17:10 -0400"  >the new feature will be available in ver 1.2</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                        <customfield id="customfield_11470" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_11170" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i00ixz:</customfieldvalue>

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