h4. It is possible to set permissions and pages up so that no one can log in. If this happens, it's necessary to reset the portal database to defaults. This is a procedure for doing so.
To do this, from a root shell:
{code}
# /etc/init.d/groundwork stop gwservices
{code}
then from a root mysql cli:
{code}
drop database jbossportal;
create database if not exists jbossportal;
grant all on jbossportal.* to 'jboss'@'localhost' identified by 'jboss';
{code}
than back at root shell:
{code}
# /etc/init.d/groundwork start gwservices
{code}
This will wipe out all non-default users and passwords, as well as any custom portal pages, dashboards, etc.
It's a good idea to back up the jbossportal database before customizing dashboards to avoid this problem.
To do this, from a root shell:
{code}
# /etc/init.d/groundwork stop gwservices
{code}
then from a root mysql cli:
{code}
drop database jbossportal;
create database if not exists jbossportal;
grant all on jbossportal.* to 'jboss'@'localhost' identified by 'jboss';
{code}
than back at root shell:
{code}
# /etc/init.d/groundwork start gwservices
{code}
This will wipe out all non-default users and passwords, as well as any custom portal pages, dashboards, etc.
It's a good idea to back up the jbossportal database before customizing dashboards to avoid this problem.