> > Midgard now can be used as a source of authentication
> information for
> > regular Apache sites using standard Apache's directives.
>
> It is enabled whereever MidgardEngine is on. That has been
> corrected in
> CVS
> which makes it possible to have it active separately.
>
> >
> > "After a migration from 1.4beta4 to 1.4beta5 the
> autentification admin site
> > is OK (SG0), but for all other site groups the logon tell
> (???) and can't
> > validate."
>
> Can you rephrase this?
>
Ok sorry fot my ugly english !!!
I designed a site with Midgard 1.4beta4 : on the root site internet
www.xxx.com/ without authentification and an intranet site with
www.xxx.com/intranet with authentification.
These sites have both a site group "internet group" and "intranet group".
Like http://marc.theaimsgroup.com/?l=midgard&m=96321000808440&w=2
With the Midgard 1.4beta4 the acces right is for all on the internet site
and on the intranet side
the logon popup is :
Enter network password
Site: www.xxx.com
Realm: Midgard
User Name: xxxxxx
Password: yyyyyy
After a update to Midgard 1.4beta5a the authentification don't work anymore.
And le logon popu is :
Site: www.xxx.com
Realm: (???)
User Name: xxxxxx
Password: yyyyyy
But the admin site is ok with :
Site: www.xxx.com
Realm: (SG0)
User Name: xxxxxx
Password: yyyyyy
So what I made wrong ?
Regards
Erwin
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
