blogs

tagging/folksonomy support in drupal

|

[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

thougths on vocore end user data collection

[phpwiki]
had thought earlier today that an alt solution to doing the mod
for sympa to get the netid map to email is to just have an external code
that does the user registration and then have sympa do an ldap lookup
against this db to get the netid map to email. conversation with jason
suggested one could avoid the ldap lookup and just pass the email to
sympa. this is true if the sympa is a consumer app, but when it is the
vocore then it needs to be the one acting as the AA backend, so it can't
consume it's own attributes (unless the AA queried across two dbs or the
reg front-end populated the user_table in sympa completely, which maybe

Re: Target-to-target communication?

Hi Tom,

Sorry to have taken so long to respond. We had a network issue locally
that took my attention away from this for a few days.

Here's a first pass at some annotation. I wanted to keep the diagram
light and mainly to identify the components in the solution so I left
out the flow. I'll try to clarify below. Let me know if I need to take
another pass.

It will probably be best to identify the goal and major components first
and then discuss the flow between components. The basic idea is to
build the foundation of a consistent system environment that can be
leveraged by participating applications, much like what we're accustomed

oasis docs

the oasis docs are hard to wrap your mind around. the two that sesm most
referenced in the early part of the shib architectural overview are
samlcore (which defines the message structures) and samlbind (which
describes how to transport saml in protocol). samlbind identifies a
mapping of saml to a protocol as a binding and defines the rules for
packing and unpacking into that protocol as the saml profile. maybe i've
just been reading to much of this today and it's all bleeding together.

mapping abstractions between tools

|

[phpwiki]
an issue to deal with when picking an application as the vocore is that
you'll need to map its abastractions and terms into the general system
environment. for example, we're using a mailing list as the vo core which
speaks of lists and subscribers. this is a general groups and members
concept. unless web interfaces are redefined to use a vo-specific naming
convention then users need to map these concepts themselves.

an advantage of using a mlist as the vocore app is that end users can
self regsiter for group membership and there is a concept of administrator
approval for membership. another aspect is that this instantly gives

globus path interference

|

[phpwiki]
We need to be cautious about following globus/vdt instructions to a tee.
One of the things that seems to be happening is that the PATH is getting
redifined to put all the globus software first. While this is ok for end
user accounts, it's not ok for root. We need to make sure that root does
not have it's path defined to include globus tools. Case in point, if
globus is in the path and you restart sshd you'll get the globus sshd.
This is not desirable. This path redefinition can also be problematic
when building software (even as an end user).

How to create and use a patch in Linux

(Copy from http://www.cpqlinux.com/patch.html)

Creating a Patch File:


diff -Naur olddir newdir > new-patch

- or -

diff -Naur oldfile newfile >new-patch



A Note concerning Patch and the number of Directory Levels used:


Try to make sure when creating a patchfile that you have the same number of directories levels for both the olddir path and newdir path. For Ex:

--- old/modules/pcitable	Mon Sep 27 11:03:56 1999
+++ new/modules/pcitable	Tue Dec 19 20:05:41 2000

The above diff would work ok as a patch.

--- old/try1/other/modules/pcitable	Mon Sep 27 11:03:56 1999

compiling shib with embedded mysql

|

seems that the problem to compiling shib with the embedded mysql server
is not in the shib configuration but in the mysql_config script
distributed with mysql. this script lists the libraries needed to link
the mysqld embedded server and seems to ommit "-lz" (the compression
library) for the libs needed to link the embedded server. adding this lib
to the shib ./configure script works around this problem. you can simply
do a:

LDLIBS=-lz ./configure ...

This seems to be a problem with the 4.1.10 mysql rpm from mysql.com and
doesn't fix itself even when I build the rpm locally.

shib attribute cache store

| |

doesn't look like its worth trying to get existing mysql session mgr for
shib working since comments describe it as a two level cache with the
attributes remaining in ram. will need to look at this more closely.
don't need to worry about it for now. need ldap database and vo mgm up
more pressing.

would need to build a attribute cache backend that stores the attributes
into the voaa origin aa cache or build that shib shim that captures the
attributes during the vo origin hs processing after the shib
authentication is done.

can't compile test code for embedded mysql

|

[phpwiki]
have had no luck with the test code and can't figure out why it's failing.
google doesn't seem to be of help. mysql.com doesn't seem to indicate any
problems with mysql embedded. and my test embedded build absolutely
refuses to link. if i do the build/link in one step i get an undefined
function mysql_server_init, if I do it in two steps I get complaints about
references to compress which I can't figure out how to resolve.

there doesn't seem to be anything special about linking the embedded db
according to the docs. the only diff between embedded and non-embedded is
that mysql_init_server() is not an empty stub in the embedded version.

Syndicate content