on 2022 Jun 01 7:48 PM
What is the use of maintaining the Authorization object in SU24 rather than in PFCG ? As we are adding the missing Authorization objects manually in pfcg then what is the need of maintaining that in SU24 ? And if we delete a tcode from the role after adding an Authorization object to the role , then what will be the impact of the Authorization object to the role from security perspective ?? Please answer it's urgent
Request clarification before answering.
If I maintain additional Authorization object in SU24 to a certain t-code , then the T-code will updated throughout the system with added authorization Objects , but it can be a risk for all the roles that are associated with particular T-code ? isn't it ?
If we maintain that authorization object in the PFCG then it will only affect to the role, not the whole system . If we delete the T-code in the role then the added authorization object will be available in the role , in that case what should we do ? Because its not possible to remember all the authorization objects that we have added manually because we are deleting the T-code in the role , not the object associated in the role . So what should a security consultant do in this type of particular case ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.