I have CAS 4.0 from git and am attempting to use the ldap integration to authenticate against Active Directory. We do not allow anonymous bind and need to bind before resolving the user dn. I can't figure out how to wire it together to get it to bind before doing the search.
Any suggestions? Mearl Danner Systems Programmer Samford University Technology Services http://www.samford.edu From: Scott Battaglia [mailto:[email protected]] Sent: Friday, June 21, 2013 1:21 PM To: [email protected] Subject: Re: [cas-dev] Recommended development environment for add-ons? You should just be able to develop it however you want in whatever IDE you want. You can probably even use whatever build tool you want as long as it can pull in dependencies from a Maven compatible repository (Maven, Gradle, and Ant+Ivy should all be able to do that). Just declare a dependency on the appropriate CAS modules. On Fri, Jun 21, 2013 at 1:53 PM, James Sumners <[email protected]<mailto:[email protected]>> wrote: I was really just using that one as an example of the type of add-on (e.g. as opposed to a site customization or client add-on). Looking through cass-addons.iml, though, I see that you're merely using cas-server-core as a dependency for the project. I wasn't sure if I need to develop a module within the CAS source tree, as a subrepository, or some other way. ~ James On Jun 21, 2013, at 1:07 PM, Misagh Moayyed <[email protected]<mailto:[email protected]>> wrote: > CAS-addons comes with the ".iml" project file for IntelliJ, which you > should be able to use to import the project into your workspace, once you > have forked and cloned the repo of course. I am not sure if you import the > codebase into Eclipse though; for some reason it's not happy about some of > the Groovy classes. As for CAS itself, eclipse (with the maven plugin > installed) or IntelliJ would be fine. > > You'll also need Maven3 and Tomcat7. > > If you wish to develop add-ons, pull requests are heartily welcome to > either project. You could try with the following git workflow: > > 1. Fork the repo > 2. Clone the forked repo > 3. Import project code into your development environment (Eclipse, > IntelliJ) > 4. Create the topic branch for the feature you have in mind > 5. Change, commit, push to the forked repo > 6. Create a pull request > > Misagh -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[email protected]> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[email protected]> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
