If you use rewriting rules to define the login path that triggers a pubcookie weblogin (or any ssl-based url reference) and you get a "not found" error from the web server after you successfully log in, make sure you have enabled the rewrite rules in the SSL vhost. Rewrite rules and engine settings don't inherit to vhosts by default so you need to do a RewriteEngine on and RewriteOptions inherit for each vhost you want the global config to influence.

The main switch to our network has been replaced. This should alleviate
the network interruption issues we've been having this past week.

Let me know if you notice any problems or any unexpected improvements.

~jpr

[phpwiki]
silbia's been working on getting the dependancies in place for
trac and subversion. in helping resolve some of the issues it seems trac
uses the one true templating system called clearsilver. after having
looked at the drupal templating options (thankfully nicely seperated via
the theme engine) where folks hype phptemplate and template toolkit. also
working with sympa where template toolkit is used. it seems that every
template tool vendor has the perfect solution. the one that you need to
use. guess that's a sure sign that the best way hasn't been discovered
yet.

finally got my sympa work under cvs. that just took too long. nothing
wrong with the process, it's just tedious to do this after the fact. much
better to get it under source control to start with than to try to back
port it later. :(

now I can work on merging this up to the 5.1 code base. I'd like to get
this with the nice new look.

probably need to get the wayf thing working first though. can't seem to
get the picture in my head on how to do this. i need a wayf for the vocore
and a wayf for the federations. the vo core wayf should be able to direct
the user to their prefered home institution regardles of what

the title says it all. i finally got off my but and submitted the patch
to the sympa developers to support seperation of identity and email during
authentication in support of shibboleth and myvocs. many thanks to the
sympa team in helping develop this patch.

[phpwiki]
been looking into the updates that would be needed to support folksonomy in drupal, known as free tagging. i like the idea of letting the end user determine the vocabulary for entries. I looked at the [drupal support for tagging|http://drupal.org/node/20936]. it really needs it to allow end-user control over vocab. from the description of the features, though, it seems like it needs some work to add features. i'd like to get the [wordpress features jim described|https://mywebspace.wisc.edu/jamesphelps/web/WordPress/wordpress_folksonomy.html] because in order to use tags in a meaningful way, you really need to have a list of popular tags to choose from or reference.

[phpwiki]
this idea has been rolling around in my head for a while and the thoughts
on tagging seem to make it an even more powerful option.

bayesian filters for spam seem to be a good way to train a filter to
answer a simple yes/no question about a given piece of content. "yes this
content belongs in catagory x" or "no this content does not belong in
catagory x". Normally the catagory is "inbox". After a while of training
the filter should get pretty good at identifying terminology patterns that
associate something with catagory x or not. if you think of each person's
inbox as a distinct catagory, then there are obvious millions of distinct

[phpwiki]
Looks like tagging support has been added to drupal 4.6 (and provides more
motivation to upgrade the @lab site). This is a logical extension to
durpal's already strong taxonomy support. The major enhancement is that
it makes term creation an end-user feature rather than restricting it to
admins.

http://drupal.org/node/20936

A sketch for the "Grid Auth in a non-kerberos environemnt" with details for the paper. the dotted black line is the technology that kx509 (ie. grid auth in a kerberos environment) would have provided us. the other components are what make up the entire solution of web sso for grid authentication.

[phpwiki]
some random reflections on what it means to have a bug.

the first part, of course, is the discovery. this can consume significant
time in tracking it down. it may turn out to be a local bug, ie. a
misconfiguration, or an actual bug in the code.

once the cause of the bug is discovered, fixing it can be as simple as
adding a line or two of code. this can get you up and running quickly and
avoid having the bug interfere with production.

an important part of using open source is reporting the bug to the
developers. each site should advertise some method to do this. projects