Quantcast
Channel: SCN: Message List - Security
Viewing all articles
Browse latest Browse all 5338

Re: Structural Authorisation Portal Vs Backend issues

$
0
0

Hi Lars Eisenberg

 

Many thanks indeed for your reply, but I have several questions with this suggestion

 

Currently we have not switched  on

AUTSW NNCON                1              HR:Customer-Specific Authorization Check (Context)

AUTSW NNNNN               0              HR: Customer-Specific Authorization Check

 

We are just using P_ORGINCON, if I switch on this custom  does it mean I will have to redesign all roles and include the new object P_NNNNNCON ie replace P_ORGINCON with this or can the two work in parallel?

Ideally I am looking at a solution whereby I just update the XXS role i.e the ESS or the MSS role.

 

Kindly help me clarify the above, I just want to be sure before switching it on. I also assume that this is reversible ie I can simply switch off the switch if thing don’t work as desired right?

 

Thank you.

 

Andy


Viewing all articles
Browse latest Browse all 5338

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>