[Deploying Sakai] means of limiting access (logins) to sakai development instances

Steve Swinsburg steve.swinsburg at gmail.com
Thu Apr 18 17:37:20 PDT 2013

We just used IP restrictions, locking down access to the dev box to the
applicable subnets. That way the code and config for the LDAP provider
between dev and prod doesnt need to be any different.

On Fri, Apr 19, 2013 at 12:18 AM, Hardy, Henry E. <Henry.Hardy at tufts.edu>wrote:

> We would like to limit access to some of our development sakai instances
> and we would like to know how you all might have accomplished this for
> instance, using LDAP or other means.
> --HH
> Henry Edward Hardy
> Senior Systems Administrator
> Tufts Technology Services (TTS)
> 169 Holland Street
> Somerville, MA 02144
> Tufts University
> +1-617-627-3068
> it.tufts.edu<https://exchange.tufts.edu/owa/UrlBlockedError.aspx>
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
> TO UNSUBSCRIBE: send email to
> production-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20130419/30296607/attachment.html 

More information about the production mailing list