This content has been marked as final. Show 4 replies
This is a standard security check which is part of CHECKIN_* services.
If you do it from GUI you won't be able to select the security group to which user has not necessary permissions. If you do it from a program (RIDC, WS, etc) you request will fail, and you will get an error message in the response.
I'm not sure I completely follow you with the "privilege".
To answer your question, yes, you may enhance behaviour of standard services such as CHECKIN_UNIVERSAL via so called "filters". Filters are Java pieces of code, that might be hooked to "filter events" such as validateCheckinData. When a service is being processed, the filter code is triggered on that event automatically.
However, the checkin services already contain a security check (it calls a Java method from the standard code), and it will do checks like "can this user check in a document with such a security group?" or "does this folder exist?", no extra code needed. So, I'm not sure what your enhancement would do additional.
If you are in a service, you can call the method checkSecurity() which is inherited from intradoc.server.Service. This is the main security method called from services.
The intradoc.shared.SecurityUtils class may also be of help: http://jonathanhult.com/intradoc-api/intradoc/shared/SecurityUtils.html