| Approach towards Login-Authorization functionality [message #110406] |
Thu, 23 October 2008 18:27 |
Eclipse User |
|
|
|
Originally posted by: spanprevention-nursubscriptions.gmail.com
Hi,
I was reading up on standard/recommended/prescribed approaches for
implementing login and authorization for RAP apps. This includes
disabling/making invisible UI features (e.g. menu items, views) that are
not authorized for certain user groups. I came across the following links:
1.
http://dev.eclipse.org/newslists/news.eclipse.technology.rap /msg01691.html
- The solution here is relatively simple and easy to implement.
2.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=201052 - As a result of this
bug, the following paper was presented as a way of incorporating a
standard login/auhtorization framework within RCP.
http://www.bredex.de/en/rcp-auth/paper.html
There is also a sample application included in the above link.
The first approach is perhaps relatively easy to implement, however if the
2nd approach is indeed a recommended/standard one, i would be interested
in investigating it further.
The question i have is: Will the above (2nd) approach also work for RAP
apps where there may be multiple users simultaneously logged on. I get the
impression that rights management is maintained in the platform, hence
common for the runtime, and not per user. If a user with elevated
privileges logs in first and while she is still logged in, a user with
normal privileges logs on, will the elevated rights of the first user
disappear because these rights are maintained by the platform for the
entire runtime? If so, what changes (if possible) can be done to alleviate
this situation? Alternatively, is it that this approach will in fact work
with RAP with little or no tweaking?
Any pointers, experiences, suggestions are much appreciated.
TIA,
Best Regards,
-abhi
|
|
|
Powered by
FUDForum. Page generated in 1.19629 seconds
] 
Search
Help
Register
Login
Home
