Hi Sands. Thank you for your response. I indeed checked the classes that implement AuthenticationMethod interface. As i mentioned earlier, the Harvard university's requirement is to authenticate the user using the Access Management System(AMS) which is a web application which speaks to the LDAP, already in place and is used by almost all applications here. So basically i am looking for making dspace redirect to the AMS login screen by a button click on dspace login page. Now AMS has to do the user login, and if successful has to return back to dspace flow, where many usecases like initEperson, adding/deleting user to groups etc has to be done, and finally a status page in dspace has to be shown abt the users memberships to groups in dspace.
Its not like dspace directly doing the LDAP communication. I am stuck as of how cocoon flow scripts and sitemaps can aid me. or do i need to do something , going out of cocoon. Please reply. Thanks and Regards Flemion. OIS, Harvard university Library. At 08:52 PM 9/2/2008 -0400, Sands Fish wrote: >Hi Flemion, > >Are the requirements that can't be fulfilled within the confines of >the stackable authentication framework (i.e. "implements >AuthenticationMethod")? Have a look at some of the other classes >that implement that interface (e.g. >org.dspace.authenticate.LDAPAuthentication). > >- Sands Fish > > >On Sep 2, 2008, at 3:44 PM, Flemion Shafeeq wrote: > >>Dear All, >>We are trying to customize authentication by making dspace speak to an >>access management system(our in house web application which >>connects to the >>LDAP). >>So in addition to the current verify email -> create Profile >>process we are >>also trying to trying to create epersons if they are available in >>the LDAP. >>We use dspace 1.5 xmlui, and the current registration process flow, i >>believe is all embedded in the sitemap, eperson.js.Since am new to >>cocoon, >>i am confused as of how dspace would communicate with an external >>application, using cocoon, etc. >>Our design is that if successfully authenticated, the external access >>management system returns a cookie, with some user details, which >>we use it >>to create the eperson and do other authorizations. >>Can somebody throw light on how dspace can communicate with the >>external >>application, and then receive back the cookie etc. >>Hope somebody have developed in similar fashion. >>Please revert. >>Thanks and Regards >>Flemion, >>OIS, >>Harvard University Library. >> >> >> >>---------------------------------------------------------------------- --- >>This SF.Net email is sponsored by the Moblin Your Move Developer's >>challenge >>Build the coolest Linux based applications with Moblin SDK & win >>great prizes >>Grand prize is a trip for two to an Open Source event anywhere in >>the world >>http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>_______________________________________________ >>Dspace-devel mailing list >>[email protected] >>https://lists.sourceforge.net/lists/listinfo/dspace-devel ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
