I committed a pile of code to the woodchip repository today. http://svn.open-ils.org/trac/Woodchip/changeset/4
This code, when run in a configured OFBIZ instance, does the following: 1. User navigates to https://localhost:8443/woodchip/control/TestAuth?externalLoginKey= <Evergreen-auth-token> 2. UserManager verifies the authtoken is for a valid Evergreen user 3. UserManager checks to see if the user has a UserLogin object in the OFBIZ db. If not, it creates a UserLogin object, which links back to the Evergreen user id, and a Person object (for the party manager), which is linked to from the UserLogin object. It also overrides the default permission class and (currently) returns true for just enough permission checks to log in. This performs enough logic to allow staff to login (via URL from the staff client) and be registered as a Party (a Person is a Party). Once you are a Party, you can do all kinds of cool stuff in OFBIZ. More on permissions later... ----------------------- Configuration add <load-component component-location="${ofbiz.home}/applications/woodchip"/> to applications/component-load.xml add woodchip/build.xml to the 'files' attribute of <filelist> near the top of applications/build.xml add <security name="default" class="org.open_ils.acq.Security"/> to framework/security/config/security.xml run 'ant' from the top-level directory to rebuild everything (or just $ ant -f applications/woodchip/build.xml). Restart. The code is experimental at this point... -bill -- Bill Erickson Equinox Software, Inc. [EMAIL PROTECTED] http://esilibrary.com/
