Bob Harner wrote:
Nice. I haven't had a chance to fully test it, but it does look good.
The other area I am concerned about is the access-control.xml files. I
use templates to offer looks, but my sub-publications have nothing in
common so they need their own passwd and policies directories. Once you
load the publication, you're stuck with the ones it was set to. We could
just make it so that each new publication has its own passwd and
policies directories and is properly configured to use them.
But wouldn't that change make it harder to have multiple publications
share the same authentication mechanisms? My sites, for example, all
authenticate against the same LDAP repository.
Well, it could be a an option. And no it wouldn't have to. When you
create a sub-publication, by default it uses one of its parent's user
directory information. So if you have Parent A, and Child X and Child Z.
If both Child X & Z are using Parent A's authentication, then users in
any of the three publications can log into any of the other three
publications.
For me, Parent A is a certain look and feel. Child X and Child Z are two
completely different school districts. They both go against my
authentication mechanism, but teachers in one school shouldn't have
access to the other district's site.
There are instances where you could go either way. My point is once the
publication is loaded, your stuck with the way you have until you
restart the application server. If people are going to be automatically
taken to their new publication, this is another area that needs to be
addressed, because no matter which way we choose, there will be people
negatively impacted. Perhaps an option to choose when creating a new
publication would work best here.
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
