Have you ever set up the Enterprise release with OBIEE or another security model only to find something got screwed up and we have locked you out of Publisher? If so, read on ...
I have to thank Mike for digging up the solution. We use a configuration file to store security information including whether you want a local superuser or not. Its always a good idea to set this up no matter what the security model you want to use - company security policy not withstanding of course.
Just locate the following file in your base Reports directory
...XMLPAdministrationconfigurationxmlp-server-config.xml
You will be able to reset values to the following
You will be able to reset values to the following
<property name="SUPERUSER_PASSWORD" value="admin"/>
<property name="SUPERUSER_USERNAME" value="admin"/>
<property name="GUEST_FOLDER" value="false"/>
<property name="ENABLE_SUPERUSER" value="true"/>
<property name="SECURITY_MODEL" value="XDO"/>
Of course you can set the super user name and password to your choice and although initially stored as a clear text password once you bounce the server for the changes to take effect the password will be encoded. The SECURITY_MODEL property when set to XDO will reset the security to native Publisher security so be careful updating that if you have created folders and roles based on EBS or database users/roles/responsibilities.
