Debug custom logon screen (SAPSYS user vows)

[Former Member]

Hi,

I am developing new login screen for e-Recruiting.

If user is trying to access the webdynpro application that requires user to be authorized in SAP, the error page shows up, configurable through tcode SICF, tab Error Pages, sub-tab Logon errors.

We chose System logon option, and then I created and assigned my own logon class ZCL_ICF_LOGIN, inheriting from CL_ICF_BASIC_LOGIN. Now, what I want is debug some methods inside my class. That is where the problems start - turns out the login class is executed under SAPSYS in client 000. I followed suggestions from http://scn.sap.com/thread/16135, both trying to create a dialog user SAPSYS in client 000, and trying to put infinite loop into my method and trigger debugging from SM50, and failed.

Option with dialog SAPSYS failed when I tried to set debug user to SAPSYS (in client 000, of course):

Option with infinite loop failed in SM50 after I selected process and chose Administration -> Program ->Debugging:

So my question is: does anybody know of a way to debug logon-screen-type applications?

[Former Member]

Hi Alexi,

What ever the screen is , weather it is a custom developed screen or it is a default screen , we can debug it by using the tcode "/h". After giving the tcode , you will get the message that "debugging is switched on". Then press enter which will take you to the debug mode.

Thanks,

Karthik.

[RaymondGiuseppi]

- Hackers would be happy if this is allowed

- Debug is subject to authorization (S_DEVELOP Development object DEBUG)

Regards,

Raymond

[Former Member]

Ya, What i said wil be possible only if you have that authorization .. , But please remember first we need to be inside the GUI for entreing the TCODE, So it is very easy to track who changed what.There is no chance of Hacking in this.We can take it as "referring to the standard code how it works"

[yuri_ziryukin]

Hello Alexei,

I'm not sure if it's possible, but maybe you can try to make the SAPSYS user a dialog user with S_DEVELOP authorization. Maybe then you would be able to debug it via SM50.

Otherwise, if nothing works, maybe you can use a combination of an ABAP trace (via ST12 for example) and some log files/log tables that you can populate inside your coding. Sounds complicated though

Cheers,

  Yuri

[eozkan]

Hi Alexi,

I know it's been a while since you posted this. Replies to this post so far are underestimating the problem. I am having the same issue at the moment. Did you find a solution by then?

Thanks

Emre