Results 1 to 2 of 2

Thread: Replacement for Weblogic run-as EJB config for data access

  1. #1
    Join Date
    Apr 2005
    Posts
    14

    Default Replacement for Weblogic run-as EJB config for data access

    Environment:
    Weblogic 8.1
    JDK 1.4
    Spring 1.1.5
    Hibernate 3

    When switching from EJB based data access to Spring/Hibernate we are facing this problem:

    Our datasources are only available to a special system user.
    All our data access goes through EJB facades.
    The facade EJBs are configured to "run-as" the system user.

    Now we are switching to data access directly through Spring/Hibernate DAOs. Does anybody know how we can achieve a similar temporary swithching of current Weblogic user in this scenario?

    By the way; Switching to Acegi is a no-op. We have to keep our Weblogic-based security.

  2. #2
    Join Date
    Feb 2005
    Location
    Boston, MA
    Posts
    1,142

    Default

    Since you are not using EJBs, you'd have to specify the run-as in the servlet's deployment descriptor. Or you could call the Weblogic security API yourself, if you wanted to only run particular parts using a particular user.
    Bill

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •