Skip to Content

Check authrozation problems in WebDynpro

Hello,

In SAPGUI there exists a tool for analysing authorization errors (go in a SAPGUI menu to System->Utilities->Display Authorization Checks or start transaction code SU53). The tool display which authorization check has failed and displays the current user setting for the failed authorization object. The tool is important e.g. for system adminstrators in order to quickly analyse authroization problems.

In WebDynpro screens I didn't find that functionality. How would I analyse authorization problems for WebDynpro applications?

Best regards,

Matthias

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Sep 21, 2007 at 04:37 PM

    Hello, Matthias,

    I believe that when you have and AUTHORITY-CHECK within your WDA component, if this check is not successful, it will generate an entry on t-code SU53.

    If you need to display in your wda component the same information SU53 displays, I believe you'll need to develop it, because I think there's no such tool in WDA.

    Regards,

    Andre

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 21, 2007 at 08:42 PM

    Hi Matthias!

    There is a simple way to find out the root cause of authorization problems (maybe even more simple than using SU53). Use transaction ST01 to activate an authorization trace. But you should filter the trace to your specific user before you activate it.

    Then process your application.

    Then goto ST01 again and stop and display the trace.

    Note: If the trace is empty the user even was not able to login due to several reasons (password, locked, expired etc.). In this case you should investigate ICM trace file ...

    Hope this helps.

    Regards,

    Volker

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.