Hi,
I have a problem
implementing a custom security implementation for an existing project. The old
project code contained some custom methods to detect whether a particular user
could edit nodes. I'm now attempting to rewrite these methods via an MMBase
implementation.
In these methods I
can obtain the current security implementation
(MMBase.getMMBase().getMMBaseCop().getAuthorization()), I can obtain the cloud
(request.getSession().getAttribute("cloud_mmbase")) and from the cloud I can
obtain the user (cloud.getUser()). However, this user is an implementation of
org.mmbase.bridge.User. All methods in the authorization implementation only
accept an org.mmbase.security.UserContext that cannot be obtained by any
means.
I would like to call
myAuthorization.check(UserContext, int, Operation) from this method, but this is
impossible.
Does anyone have a
solution for this problem?
Regards,
Ronald
Wildenberg.
-----------------------Disclaimer-------------------------
Dit bericht (met bijlagen) is met grote zorgvuldigheid samengesteld. Voor mogelijke onjuistheid en/of onvolledigheid van de hierin verstrekte informatie kan Kennisnet geen aansprakelijkheid aanvaarden, evenmin kunnen aan de inhoud van dit bericht (met bijlagen) rechten worden ontleend. De inhoud van dit bericht (met bijlagen) kan vertrouwelijke informatie bevatten en is uitsluitend bestemd voor de geadresseerde van dit bericht. Indien u niet de beoogde ontvanger van dit bericht bent, verzoekt Kennisnet u dit bericht te verwijderen, eventuele bijlagen niet te openen en wijst Kennisnet u op de onrechtmatigheid van het gebruiken, kopiëren of verspreiden van de inhoud van dit bericht (met bijlagen).
This message (with attachments) is given in good faith. Kennisnet cannot assume any responsibility for the accuracy or reliability of the information contained in this message (with attachments), nor shall the information be construed as constituting any obligation on the part of Kennisnet. The information contained in this message (with attachments) may be confidential or privileged and is only intended for the use of the named addressee. If you are not the intended recipient, you are requested by Kennisnet to delete this message (with attachments) without opening it and you are notified by Kennisnet that any disclosure, copying or distribution of the information contained in this message (with attachments) is strictly prohibited and unlawful.
----------------------------------------------------------
