03-05-2014 6:50 AM
Our company restrict the authorization of debug. I know the authotizationg object is s_develop. But I do not know what the authorizationg control. What is the risk of the debug?
03-05-2014 8:44 AM
Hi Zhang,
Due to security reasons, debugging access to production system might be restricted.Because in production server the client live data exists .There are chances that while debugging one can edit the entries and commit work,which impacts on client data(business).
Regards,
Manasa Veena P.
03-05-2014 7:34 AM
Hi,
If its in production system, then they are right in doing so as in debug you can change values and run anything.
Raghav
03-05-2014 8:20 AM
Thanks for your advise. Then I want to know what the risk of the debug authorization is .
03-05-2014 8:47 AM
Hi Huiyong,
When you debug a program you can change he values in debug mode...for ex: if that is a debit memo being issued to customer address then in program you can change the address to your address and the debit memo would reach your home instead of customer's address.
To avoid that Security would not give debug access in production system and even if some clients agree to debug authorization they would remove the access to change the variables in debug.
Raghav
03-05-2014 8:44 AM
Hi Zhang,
Due to security reasons, debugging access to production system might be restricted.Because in production server the client live data exists .There are chances that while debugging one can edit the entries and commit work,which impacts on client data(business).
Regards,
Manasa Veena P.