<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: supress authentication check from within ABAP code in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/supress-authentication-check-from-within-abap-code/m-p/7611082#M1569359</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why don't you just log the requests and run a job at frequent intervals with an appropriate user ID that calls the BAPI?  Typically, self-service stuff like this (address changes, email changes, password resets) are done from an external app or portal and the underlying comm user that connects to the system has the authority to make the change.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 17 Jan 2011 16:04:57 GMT</pubDate>
    <dc:creator>brad_bohn</dc:creator>
    <dc:date>2011-01-17T16:04:57Z</dc:date>
    <item>
      <title>supress authentication check from within ABAP code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/supress-authentication-check-from-within-abap-code/m-p/7611080#M1569357</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;we want all users to update their email-address in their own sap profile. (a self service)&lt;/P&gt;&lt;P&gt;By default, in the screen "System"-&amp;gt;"User Profile"-&amp;gt;"Own Data", he can update all except his email-id.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For this, we have written an abap report.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
DATA: p_smtp TYPE TABLE OF bapiadsmtp WITH HEADER LINE,
      p_return TYPE TABLE OF bapiret2 WITH HEADER LINE,
      p_addressx TYPE bapiaddr3x.

data: p_uname TYPE xubname.
PARAMETERS:   p_email TYPE ad_smtpadr OBLIGATORY.
      
      
      p_uname = sy-uname. "logged in user

      p_smtp-e_mail = p_email.
      p_smtp-std_no = 'X'.
      p_smtp-home_flag = 'X'.
      p_smtp-consnumber = '001'.

    p_addressx-e_mail = 'X'.

    CALL FUNCTION 'BAPI_USER_CHANGE'
      EXPORTING
        username = p_uname
        addressx = p_addressx
      TABLES
        return   = p_return
        addsmtp  = p_smtp.

&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when we execute this report, with all rights, it works fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but a normal user when he executes, he is getting this error:&lt;/P&gt;&lt;P&gt;"You are not authorized to change users in group"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the su53 screen shows:&lt;/P&gt;&lt;P&gt;&lt;SPAN __default_attr="Courier" __jive_macro_name="font"&gt;
   Authorization check failed
  Object Class BC_A Basis: Administration
    Authorization Obj. S_USER_GRP User Master Maintenance: User Groups
      Authorization Field ACTVT Activity
                                                                                02
      Authorization Field CLASS User group in user master maintenance
                                                                                &amp;lt;Dummy&amp;gt;
&lt;/SPAN&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;the point here is we cannot add User Maintenance rights to all our normal users&lt;/U&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is there any way, within the report (code) we can suppress the authentication check, programatically just while calling 'BAPI_USER_CHANGE', so that the user will be able to update his email-id.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks in advance,&lt;/P&gt;&lt;P&gt;Madhu_1980&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jan 2011 11:31:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/supress-authentication-check-from-within-abap-code/m-p/7611080#M1569357</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-01-17T11:31:30Z</dc:date>
    </item>
    <item>
      <title>Re: supress authentication check from within ABAP code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/supress-authentication-check-from-within-abap-code/m-p/7611081#M1569358</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here are 2 useful links:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapdev.co.uk/fmodules/fms_updateaddress.htm" target="test_blank"&gt;http://www.sapdev.co.uk/fmodules/fms_updateaddress.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="1346896"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If these don't help the noly thing I can suggest is that you write your own bdc program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Warren.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jan 2011 11:38:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/supress-authentication-check-from-within-abap-code/m-p/7611081#M1569358</guid>
      <dc:creator>former_member201275</dc:creator>
      <dc:date>2011-01-17T11:38:03Z</dc:date>
    </item>
    <item>
      <title>Re: supress authentication check from within ABAP code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/supress-authentication-check-from-within-abap-code/m-p/7611082#M1569359</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why don't you just log the requests and run a job at frequent intervals with an appropriate user ID that calls the BAPI?  Typically, self-service stuff like this (address changes, email changes, password resets) are done from an external app or portal and the underlying comm user that connects to the system has the authority to make the change.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jan 2011 16:04:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/supress-authentication-check-from-within-abap-code/m-p/7611082#M1569359</guid>
      <dc:creator>brad_bohn</dc:creator>
      <dc:date>2011-01-17T16:04:57Z</dc:date>
    </item>
    <item>
      <title>Re: supress authentication check from within ABAP code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/supress-authentication-check-from-within-abap-code/m-p/7611083#M1569360</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;@Brad Bohn :&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;gt;Why don't you just log the requests and run a job at frequent intervals with an appropriate user ID that calls the BAPI?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for this idea, your idea meets atleast partially the requirement.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Jan 2011 05:20:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/supress-authentication-check-from-within-abap-code/m-p/7611083#M1569360</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-01-18T05:20:23Z</dc:date>
    </item>
  </channel>
</rss>

