Login Handling

[former_member193202]

hi guys,

i'm using an own login screen - copied system bsp application as the manual tells me, and now i want to use an own LoginHandler to do some own coding, but how?

i did the following in the OnInit Handler

application->request->set_form_field

( name = 'CO_BSP_HANDLER_CLASS'

value = 'ZCL_BC_WEB_LOGON_HDL_0001' ).

are there any other possiblities, as this does not work????

kind regards oliver

[former_member181879]

Look at note 517860. See the attachments section. There is a .zip file with some detailed information on SYSTEM application.

The correct way to do this, is to just add &BspHandlerClass=CL_MY_CLASS into the configuration line in ICF!

For the record, you just made a very simple mistake. Do you see it?

  request->set_form_field( 
    name  = CL_BSP_LOGIN_APPLICATION=>CO_BSP_HANDLER_CLASS
    value = 'ZCL_BC_WEB_LOGON_HDL_0001' ).

++bcm

[former_member193202]

hi brian,

yeah i got that note already, but wen i enter my class in the Handler Page in transaction SICF, i get an errormessage (class did not implement interface if_http_extension).

so your suggestions to write &BspHandlerClass=MYClass ???? but where , what do you mean with config_line?

kind regards

oliver

[former_member181879]

Hmmmm.... You did read note 517860?

<i>The appendix of this note contains complete documentation...</i>

Maybe that word "appendix" is confusing. It should mean attachments. Looking there, I see a 20 page documentation that shows you how to integrate into ICF. Nothing about specifying an owner handler class. You have to specify your own error handling URL.

You can also consider to read the online documentation. This whole process is described very well.

http://help.sap.com/saphelp_nw04/helpdata/en/1d/13c73cee4fb55be10000000a114084/frameset.htm

Maybe you should look at the ICF node for SYSTEM_PRIVATE very carefully.

++bcm

[former_member193202]

hm,

i think you missunderstood me, rederection to the error page already works etc.

i made the things as described in the docu starting with "copying system-application"....

and there is a hint how to make an own bspHandler for small coding enhancements:

IMPLEMENT YOUR OWN CLASS WHICH IS DERIVED FROM CL_BSP_LOGIN_HANDLER blablabla , and then, THEN CONFIGURE SYSTEM SO THAT IT USES YOUR NEW HANDLER CLASS....----> and my question is how to do that?????

[Former Member]

Hello Oliver,

well, the answer is: extend the the path of "redirect url" in the sicf node of your bsp in the tab for error pages as you did alreay.

Add the following: "&BspHandlerClass=CL_BSP_LOGIN_HANDLER"

Replace standard handler class by your own class.

I think that's what Brian tried to explain to you.

Regards, Bernd

[former_member193202]

yeah now it works perfectly,nearly

what i do is than calling susr_internet_userswitch to change from service to dialog user but where the hell do i make the link between service und dialog user????

kind regards

oliver

[Former Member]

Hello Oliver,

hmm, user switch ?

Actually I use the same technique than you do now, but I don't do any user switch.

The system/login.htm - or the copy of it - uses client 000 and the standard user "SAPSYS" for the logon in the public area.

If the logon data are correct the redirect will do the creation of the SSO-Ticket for the logged in user automatically. To my current understanding there's no need for a user swith.

Regards, Bernd

[former_member193202]

hello bernd,

hmm, okay let me tell what we want to do - maybe that's not possible??

Login As SERVICE-User in the PUBLIC/COMMON area and then - at a given point - switch to a DIALOG-USER , so maybe n service-users swith to some/one different dialog-users, with is done with SUSR_INTERNET_USERSWITCH....

The point behind is:

we give our users service-users for browsing some kind of public sites, and when they want to do some proteced things the user is switched to the dialog-user, which is related to the service-user he has logged into system.

see documentation of SUSR_INTERNET_USERSWITCH where the behaviour we're willing to use is described.

kind regards,

oliver