Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
To log into AdminCentral, go to:
- Author instance -
- Public instance -
The generic form of the URL is
http://<domain>:[<port>]/<contextPath>/.magnolia. It may be different on your system.
Session Timeout After user Inactivity
The session timeout defines the allowed time of inactivity after which the user must login again. The session timeout for the Magnolia AdminCentral is bound to the session timeout of the underlying servlet container.
For instance on a Tomcat server the session timeout is configured per web application in the
web.xml and looks like this:
Demo user accounts
Full access. Equivalent to root account on Unix systems.
Editor. Can add and edit content and start a publishing process.
Publisher. Can only read content and approve publications.
Superuser is the admin account that has access to everything. Accounts
peter are created by the travel demo. If you can't log in as
peter, log in as superuser and create users for your site.
Accounts are automatically locked out after N+1 failed login attempts, where N is a number configurable at Configuration >
With Magnolia you typically get an example travel demo site. It showcases essential features. The demo is also available online at demo.magnolia-cms.com.
The demo is reset every 30 minutes. We recommend that you download install your own copy Magnolia so you won't lose your work.