Reg User Exit SUSR0001

[Former Member]

Hi all,

Facing problem with user exit SUSR0001.

When we login through GUI control is flowing through the exit, but when we login

through RFC, control is not flowing through the exit.

Wt to do if we want need any validation while we login through RFC.

Suggestions pls.

Regard's

Jean.

[Former Member]

Hi all,

Facing problem with user exit SUSR0001.

When we login through GUI control is flowing through the exit, but when we login

through RFC, control is not flowing through the exit.

Wt to do if we want need any validation while we login through RFC.

Suggestions pls.

Regard's

Jean.

[kesavadas_thekkillath]

When i checked the where used list

The function module EXIT_SAPLSUSF_001 is only used in a function module SUSR_LOGON_USER_EXIT which is not rfc enabled.

Nb:The function module SUSR_LOGON_USER_EXIT doesnt display any where used list.

[Former Member]

Hi Keshu,

Thnks for ur rply.

It is not required that the FM SUSR_LOGON_USER_EXIT should be RFC Enabled, bcoz this exit is getting triggered after logon to the system.

Regard's

Jean.

[kesavadas_thekkillath]

So you can debug SUSR_LOGON_USER_EXIT and check why its not passing through the customer function,when executed from rfc

[Former Member]

Hi Keshu,

I dont think it is possible to debug before logon to the system.

If we do GUI logon it is passing through tht exit, so we can keep brekpoint and check.

But if we do RFc logon ( eg. From SM59, through Remore logon option ) , the system directly log in to the

call system without passing through the exit. In this case where do we set breakpoint to debug.

Thnks,

Jean.

[kesavadas_thekkillath]

I think this exit gets triggered only in dialog mode.

[andrea_olivieri]

Jean wrote:

But if we do RFc logon ( eg. From SM59, through Remore logon option ) , the system directly log in to the
call system without passing through the exit. In this case where do we set breakpoint to debug.

Hi Jean,

if you use the "remote logon" option from the RFC destination, in this case, you could configure it by by setting the "Current user" flag = 'X'.

This configuration will open the logon screen of the target system and fire your userexit.

Regards,

Andrea

[Former Member]

Hi Andrea,

No if we check the 'Current User' in SM59, even then the exit is not fired.

I made it sure tht I cant use this exit.

Trying to work through some other ways.

Thnks,

Jean.

[andrea_olivieri]

Hi Jean,

before to post the answer, I did a test on my trial system.

With the flag "Current User" = 'X' you must enter username and password on the target system and then the userexit is fired....( i sent a message to my user only).

With another username, the message was not shown, so this is the evidence that the userexit works fine.

Regards,

Andrea

[Former Member]

Hi Andrea,

You might have selected 'Logon Screen' in the security options.

Offcourse if we do remote logon through logon screen, even though it is RFC the control will flow through the exit,

and i am aware of tht one.

But in my case the user wont be shown the logon screen.

We hve to look for some other solutions apart from this exit.

Thnks,

Jean.

[andrea_olivieri]

If I knew from the beginning ...

If there is no other way to solve the issue, maybe you can convince the user to pass from the logon screen in the remote system.

Afterall he has only to type a password...

Cheers,

Andrea

[Former Member]

Andrea,

Thnks a lot for ur comments.

RFC logon is possible in different ways, ( eg : Single signon, Through HTTP which we call as plugin login.....),

So I cant convince by logging through the screen which is particular through RFC destination Remote logon.

Let me try still

However thnks for ur explore.

Regard's

Jean.

[andrea_olivieri]

Jean wrote:

...when we login through RFC, control is not flowing through the exit

Hi,

usually in the RFC connections, Service user or Background user types are always specified...

These kind of users are no-dialog user and therefore the userexit you implemented is not executed.

In the link below you can find some information about RFC user management.

[http://help.sap.com/saphelp_nw04s/helpdata/en/ed/8d7b64ee75ef4cb42358427613fa95/content.htm]

Regards,

Andrea

[Former Member]

Hi Andrea,

Thnks for ur rply.

An RFC connection can also be established by dialog users, It is not like that only Service users or Reference users only can establish RFC connection.

So when a dialog user logon to the system through RFC ( may be through SM59 destinations ), he has to pass through the exit.

But it seems clearly that only GUI logon will pass through that user exit SUSR0001, now my requirement is to validate dialog users who logon through RFC Connection.

So is there any other way to validate apart from this exit susr0001.

Regard's

Jean.

[kesavadas_thekkillath]

This thread might be helpful to you.

Julius Bussche has something to say regarding this link:[;

Edited by: Keshu Thekkillam on Oct 29, 2009 11:14 AM

[Former Member]

Hi Keshu,

I went through tht thread.

I got some information, but really it didnt helped me.

Any other way to resolve it ?

Thnks,

Jean.

[Former Member]

Jean - Did you get any solution for this?

I am in the similar situation and finding the solution.

I know its quite a long time but would appreciate if you dig your memory.

Thanks

[Former Member]

Hi,

How did you solve this.

I can validate gui login using SUSR0001

Implementation of SAP logon user exit SUSR0001 - SAP ABAP,SAPUI5,SAP HANA,SAP Fiori,OData,Netweaver ...

But Which exit or badi runs when user logs via web view?

Regards