blogs

got the double shib redirect working so now we have one shib install
protected by another. this is working nicely and feeding remote user
through. now just have to set up distinct ldap database for vo and get the
open subscription id provider "id" working. also need to refine the arp
and aap so the vo system env gets a consist set of attributes from the vo
database.

• Login user automatically with user's blazerid

In index.php check if $_SERVER['REMOTE_USER'] has been set (which means pubcookie authentication is enabled) and $_USER['uid'] hasn't been set (which means user hasn't logged in). If that is the case, redirect to users.php by setting a Refresh header. I have also tried the Location header, which always leads to a pubcookie error page saying the user has already loged in.

In order to prevent user from seeing the blinking effect of redirecting, the php processing is terminated with exit() after setting the header.

got the shib infrastructure working after gaining understanding of the
keyname field in IQ-trusts.xml and shibboleth.xml. set up ~jpr/test/shib
url and successfully passed in my uid from uab ldap as the remote_user
value. long day. tomorrow i can focus on a general purpose ldap service.

i don't understand why drupal separates comments out as a distinct
content type. it seems like it would be better to consider everything as
a node, ie. inherited from a node type. this would potentially enable
a common display framework with different renders. it also seems like
having all node type be identically defined, that is no second class
types, would help make the content rendering easier. eg. the node table
types would be anything defined by the taxonomy and the base set could
be the standard story, blog, page, etc. types. the legit content would
the simply be defined by the type tag. additional tables could be used

the d**n test forum gateway isn't working, spent most of the afternoon
trying to make the forum posts look better. never found the cause of the
bad and inconsistent-across-posts formatting.

formaat with a special chcar
> thorown in for
fun

_______________________________________________
Test21 mailing list
Test21@lab.ac.uab.edu
http://metric.it.uab.edu/mailman/listinfo/test21

whats up
with the funky forum
filtering?

feel like we're getting to a good point of having our raw materials to the
point of some integration that will lead to useful outcomes. combining
the three diagrams into a developer guide book is really doable and having
the target of the that guide be the pycon2005 mailman developers seems
like a workable goal.

been entering in hardware bugs for items that are going unaddressed in
the lab. this triggered a thought that this is the shared responsibility
project we need. this is basically our equipment project. We need to
have our dell contact information published so that we all know who to
contact. we need to have the proceedures documented. we need to have a
common mailing address that we can act as the equipment manager/requestor
to dell. This is basically our vo for equipment mgmt and entails mailing
lists, wikis, we mail clients, formums/archives, etc. getting this set
up and having people participate will be our way of being virtual

[phpwiki]

it's important to redefine a website login as an application launch when
websites are merge together using middleware. the authn step by webiso is
really process initialization by the distributed kernel. this initiallizes
the uid (REMOTE_USER) of the process. the process then looks in the
user-specific initialization file (the "account" container for the web
tool). and sets values defined for that user. this is effectively using
an implicit HOME var and cwd allowing the web tool to load it's config
file. granted, this really all boils down to a select * from account
where user=somebody query