Re: [Tikiwiki-devel] Tikiwiki and Web Initial Sign-on authentication systems

[Terence <te...@gm...>]

By batch upload do you mean batch user accounts with a list of usernames?

Is Tikiwiki able to work with standard .htaccess password protections?

Thanks for your advice.

Terence

On Thu, 5 Jun 2003 15:40:17 -0300, "Luis Argerich" <lu...@fu...>
said:
> I think that mod_cas is the best option handling the authentication at
> the
> WebServer level.
> In order to assign tiki-permissions you need Tiki users.
> We have batch-upload feature for users in the current development version
> 1.7, you can take this from CVS and use it your "I guess" 1.6.1 version
> to
> be installed. Then you can just upload all the users using a CSV file and
> administer the permissions normally.
> 
> ----- Original Message -----
> From: "Terence" <te...@gm...>
> To: <tik...@li...>
> Sent: Thursday, June 05, 2003 3:27 PM
> Subject: [Tikiwiki-devel] Tikiwiki and Web Initial Sign-on authentication
> systems
> 
> 
> > Hi there,
> >
> > I am in the proccess of deploying Tikiwiki at Yale University.  Yale
> > users a Web Initial Sign-on system (WebISO,
> > http://middleware.internet2.edu/webiso/) known as Central Authentication
> > Service (CAS, http://www.yale.edu/tp/auth/cas10.html).  I was wondering
> > if anyone has experience or might be interested in helping to customize
> > Tikiwiki so that it can work with a WebISO like CAS?  I am a novice PHP
> > coder, so I'd need all the help I can get.
> >
> > Here are the basics of the CAS system:
> > 1. When user attempts to view a CAS-protected page, the user is
> > redirected to an official CAS login page where user types in
> > username/password.
> > 2. CAS sends the user back to the originating URL and passes along a
> > ticket.
> > 3. The originating page then calls CAS and validates the ticket.
> > 4. CAS either responds that the ticket is invalid, or responds that it is
> > valid and also what the username of the user is.
> >
> > http://www.yale.edu/tp/auth/cas10.html goes into much more detail but
> > this is essentially how CAS works.
> >
> > One way to accomplish this task is to insert custom code in Tikiwiki to
> > interface with CAS completely.  Another method is to use an Apache module
> > provided by Yale ITS known as mod_cas.  With mod_cas, one can use a
> > .htaccess file with AuthType CAS to protect a directory.
> >
> > Users of the Tikiwiki site will all have pre-existing usernames for CAS.
> > Ideally nobody will have to reregister with Tikiwiki.  Is there a way I
> > can still assign users to groups based on their CAS usernames (and assign
> > permission to these groups using Tikiwiki's admin system)?
> >
> > Thanks in advance for any help.
> >
> > Terence
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> > thread debugger on the planet. Designed with thread debugging features
> > you've never dreamed of, try TotalView 6 free at www.etnus.com.
> > _______________________________________________
> > Tikiwiki-devel mailing list
> > Tik...@li...
> > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
> >
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> Tikiwiki-devel mailing list
> Tik...@li...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
> 
>