<?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: SAP Security - User Buffer Behavior in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-security-user-buffer-behavior/m-p/742741#M35524</link>
    <description>&lt;P&gt;These are 2 separate instances of S_TABU_DIS and would not merge&lt;/P&gt;</description>
    <pubDate>Fri, 26 Oct 2018 17:34:50 GMT</pubDate>
    <dc:creator>sri_g4</dc:creator>
    <dc:date>2018-10-26T17:34:50Z</dc:date>
    <item>
      <title>SAP Security - User Buffer Behavior</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-security-user-buffer-behavior/m-p/742739#M35522</link>
      <description>&lt;P&gt;I am trying to determine what auth object values will be checked for a user with multiple roles and authorizations assigned to them. I have an example below;&lt;/P&gt;
  &lt;P&gt;User JDOE has the following example access roles and authorizations.&lt;/P&gt;
  &lt;P&gt;&lt;STRONG&gt;Role 1:&lt;/STRONG&gt;&lt;/P&gt;
  &lt;P&gt;T-Code: SM30&lt;/P&gt;
  &lt;P&gt;Auth Object: S_TABU_DIS&lt;/P&gt;
  &lt;P&gt;Activity: 02&lt;/P&gt;
  &lt;P&gt;Auth Group: ABC&lt;/P&gt;
  &lt;P&gt;&lt;STRONG&gt;Role 2:&lt;/STRONG&gt;&lt;/P&gt;
  &lt;P&gt;T-Code: SM30&lt;/P&gt;
  &lt;P&gt;Auth Object: S_TABU_DIS&lt;/P&gt;
  &lt;P&gt;Activity: 03&lt;/P&gt;
  &lt;P&gt;Auth Group: *&lt;/P&gt;
  &lt;P&gt;&lt;STRONG&gt;Question -&lt;/STRONG&gt; When this user JDOE executes SM30, will they have Activity 02 over ALL Auth Groups or just 02 over Auth Group ABC?&lt;/P&gt;
  &lt;P&gt;I would greatly appreciate a response.&lt;/P&gt;
  &lt;P&gt;Thank You!&lt;/P&gt;</description>
      <pubDate>Fri, 12 Oct 2018 23:52:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-security-user-buffer-behavior/m-p/742739#M35522</guid>
      <dc:creator>former_member993829</dc:creator>
      <dc:date>2018-10-12T23:52:39Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Security - User Buffer Behavior</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-security-user-buffer-behavior/m-p/742740#M35523</link>
      <description>&lt;P&gt;they will only have ACTVT 02 to the Auth Group ABC. SAP doesn't merge the fields together in the buffer. User buffer does not care which role the authorisation comes from but it does evaluate each authorisations as a whole.&lt;/P&gt;</description>
      <pubDate>Sat, 13 Oct 2018 07:35:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-security-user-buffer-behavior/m-p/742740#M35523</guid>
      <dc:creator>Colleen</dc:creator>
      <dc:date>2018-10-13T07:35:54Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Security - User Buffer Behavior</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-security-user-buffer-behavior/m-p/742741#M35524</link>
      <description>&lt;P&gt;These are 2 separate instances of S_TABU_DIS and would not merge&lt;/P&gt;</description>
      <pubDate>Fri, 26 Oct 2018 17:34:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-security-user-buffer-behavior/m-p/742741#M35524</guid>
      <dc:creator>sri_g4</dc:creator>
      <dc:date>2018-10-26T17:34:50Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Security - User Buffer Behavior</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-security-user-buffer-behavior/m-p/742742#M35525</link>
      <description>&lt;P&gt;So it is important to understand, what is meant by 'authorization'. When users/admins talk about authorizations, they often mean something different compared to what the system means....&lt;BR /&gt;&lt;BR /&gt;Technically speaking (from the codumentation):&lt;/P&gt;&lt;P&gt;quote&lt;/P&gt;&lt;P&gt;Entry in the user master record as part of an authorization profile . An authorization consists of fully specified or generic values for the authorization fields of an authorization object. The combination defines which activities a user can use to access which data. Authorizations are generated using the profile generator from role management tool (transaction PFCG) and can also be displayed using transaction code SU03.&lt;/P&gt;&lt;P&gt;unquote&lt;/P&gt;&lt;P&gt;Therefore - as Colleen has stated: each assigned 'authorization' is treated seperately and the authority-check checks the assigned authorizations for an object one by one with the values provided in the abap coding, until a positive result is found or all assigned authorizations have been checked w/o success (failed authority-check)&lt;/P&gt;&lt;P&gt;brgds, Bernhard&lt;/P&gt;</description>
      <pubDate>Tue, 04 Dec 2018 10:55:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-security-user-buffer-behavior/m-p/742742#M35525</guid>
      <dc:creator>Bernhard_SAP</dc:creator>
      <dc:date>2018-12-04T10:55:56Z</dc:date>
    </item>
  </channel>
</rss>

