Re: multimple domain authentication

> that's my point of disagreement. I'm not giving access to people not 
> known. If you're from [email protected], I might let you access my fossil 
> and I might not. If I do, you can attach it, but if not, use your fossil 
> from your domain. I don't see your point here at all. 

If you aren't giving file service access at all, then
all you need is a yes/no from the auth server and a name
to own the processes.  That's fine.

But in a system built around file-like services, I can't
imagine there not being services on the grid that look
like file systems.  In that case, I want to be able to
control remote users' access more specifically than just
yes or no for all the domains the auth server trusts.
I want to place remote users in local groups and possibly
limit access per-domain.  I think the best way for that
to happen is for the file servers that care to understand
the user@domain convention, and do something sensible
with it.

I think my original post was because I thought Andrey
suggested that file servers need never know about the
user@domain convention.  Reading back through this thread,
I'm not sure he suggested that at all.

Micah