Yesterday we have done the following migration: - replace the default authentication mechanism by one based on JAAS to authenticate against our LDAP - Migrate from Magnolia 3.01 to 3.02
This migration failed because we noticed that publication did not work anymore. When publishing we now receive an "Access denied" error message, although we haven't change anything in the configuration. The users have also been published. Has anyone already experienced the same problem? Do you think it is due to LDAP or to 3.02 migration? It seems that it is due to the LDAP but we are not sure at the moment (only the user/password data are validated against the LDAP, the rest (access rights, ACL, ...) are still declared in Magnolia Any help welcomed Regards Gilles ************************************************************************************ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager ([EMAIL PROTECTED]) and delete the message with any attached files from your system. The confidentiality and integrity of this message cannot be guaranteed on the Internet and the sender does not accept liability for its content. *********************************************************************************** ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
