User Interface Security

[Former Member]

What is the best way of securing different UI elements of the same view for different users?

[Former Member]

Hi Michael,

We had this issue and this is how we resolved it.

1) Pass a application parameter to your base application of iView. This parameter shall hold the information about role to which the user is assigned to.

2) In handledefault of window set this parameter to a context attribute which should be visible globally. Now the moment you try to instantiate your view you can check for role and decide whether the informaiton needs to visible to the user or not.

The drawback is that you cannot do it at user level, infact i really wonder in which business scenario you would need to filter information based on "User" instead of "Role".

Hope this helps.

Regards,

Anoop

[Former Member]

Anoop

Can you give me an example.

What is the name of the portal role variable of the logged in user?

I need to pass the role to webdynpro/ABAP iview/application.

I am searching for the variable name.

Thanks a lot.

[Former Member]

Hello Michael

While this may not be the best way, it works nicely. We assigned security roles to users for different functions. When the Web Dynpro component is instantiated, we checked the table AGR_USERS (role assignments) for what sy-uname is allowed to see. The roles are stored in a context node with a set of attributes (type WDY_BOOLEAN).

Then, the view element parameters "Read Only", "Visible", and "Enabled" can be linked to these values (or NOT value) to dynamically manipulate what the user can see and do.

Cheers,

Adam