Hi Bruno,
Currently Rundeck relies on the application container to do
authentication. The authentication we use with the default Jetty
container is JAAS authentication, which is implemented with a the
LoginModule interface. Here is some documentation on implementing a
JAAS LoginModule:
http://docs.oracle.com/javase/6/docs/technotes/guides/security/jaas/JAASLMDevGuide.html
For other containers, like Tomcat, you can use JAAS authentication as
well, or a custom Tomcat-specific Realm implementation. Here is the
link for Tomcat JAASRealm information:
http://tomcat.apache.org/tomcat-6.0-doc/realm-howto.html#JAASRealm
So you may need to implement authentication to the Atlassian
athentication server if there is not a JAAS login module for it
already available
On Sun, Jun 24, 2012 at 3:39 AM, Bruno Blaise <
blai...@gmail.com> wrote:
> Hi,
>
> I'm investigating the usage of RunDeck to implement a Continuous Deployment
> System. I found information and example to use it, to integrate it with
> bamboo and nexus. I'm already using RunDeck to start/stop/... the services.
>
> Our development platform is based on the Atlassian eco-system (Crowd,
> Confluence, Jira, Bamboo, FishEye) and Svn,Nexus for the code+artifacts. All
> those services are using Crowd as the authentication engine.
>
> Atlassian provides a Crowd REST API
> (
https://developer.atlassian.com/display/CROWDDEV/Crowd+REST+APIs) and a
> java client
>
https://developer.atlassian.com/display/CROWDDEV/Java+Integration+Libraries
>
> How would you implement the usage of Crowd with RunDeck ?
>
> Is-it a good approach to implement the abstract class
> com.dtolabs.rundeck.jetty.jaas.AbstractLoginModule ?
>
> or do you see a better way to integrate both of them ?
>
> Thanks in advance for your help,
> Bruno