ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Forums » Develop »

Using chili project as authentication source

Added by Daniel Nauck at 2011-09-23 08:37 am

Hello,

is it possible to use chili project as authentication source for other applications?

I want to use the in chili project registered users + groups in another application and use the chili project authentication whether the users are stored in Db or LDAP, etc.

Is there a way to do this, e.g. with the REST API?


Replies (6)

RE: Using chili project as authentication source - Added by Chris Woerle at 2011-09-26 10:35 am

i am working on this, it's pretty done.

basically: you get the user with her permissions via the api.
you will have to use some powerful (admin) account for the APIKEY

RE: Using chili project as authentication source - Added by Daniel Nauck at 2011-09-26 11:15 am

Chris Woerle wrote:

i am working on this, it's pretty done.

basically: you get the user with her permissions via the api.
you will have to use some powerful (admin) account for the APIKEY

Where can i track the progress of your work? For which chili project version is it planned?

RE: Using chili project as authentication source - Added by Chris Woerle at 2011-09-26 12:05 pm

Where can i track the progress of your work? For which chili project version is it planned?

nowhere unfortunately.
I am working on a larger project and we rather planned to merge a lot of stable work later into chili. so there is nothing planned yet.
But i think i can take care, that you don't have to wait too long.

If you'd specify more, what your client looks like, we can find out better, what you'd need in the backend.

RE: Using chili project as authentication source - Added by Daniel Nauck at 2011-09-26 12:11 pm

Chris Woerle wrote:

If you'd specify more, what your client looks like, we can find out better, what you'd need in the backend.

We want to integrate the CI Server CruiseControl.NET.
So permissions/roles/users could be shared between CCNet and chili project.

You'll find the current security docs here: http://www.cruisecontrolnet.org/projects/ccnet/wiki/Security

Thanks.

RE: Using chili project as authentication source - Added by Felix Schäfer at 2011-10-02 05:12 pm

I don't think the current API is fit to provide authentication and authorization to other apps. I've done this last year (so still Redmine) at LDAP (authentication) and DB (authorization) level.

RE: Using chili project as authentication source - Added by kiran patil at 2011-10-03 09:01 am

FYI. rubycas server(Single sign-on authentication for enterprise web apps), http://code.google.com/p/rubycas-server/.

RubyCAS-Server gives you:

  • A stand-alone central login page where the user enters their credentials (i.e. their username and password).
  • A mechanism for validating the user's credentials against various backends (a table in a SQL database, ActiveDirectory/LDAP, Google accounts, etc.)
  • A back-end validator where CAS-enabled client applications connect to check whether the current user is authenticated (if the user has already been authenticated with the CAS server, then they are permitted to proceed, otherwise they are redirected to the CAS server's login page for authentication).
  • Full compatibility with the open, multi-platform CAS protocol (CAS clients are implemented for a wide range of platforms, including PHP, various Java frameworks, .NET, Zope, etc.)
  • Multi-language localization -- RubyCAS-Server automatically detects the user's preferred language and presents the appropriate interface.

(1-6/6)