Limiting access to global.properties.xml

Currently, Enterprise Portal does not encrypt the user name and password used to log in to Portal Interface. To minimize the impact of this, set up global.properties.xml for minimal file access.

You should also change the database user name found in global.properties.xml from the default to something else. You must coordinate these changes between the portal database and the global.properties.xml file.

Limiting access to global.properties.xml

1. Use Sybase Central or isql to create a new user in the portal database and make this user the owner of portaldatabase and portalsearchdb. Here is the input using isql:

   // Create a user portalowner/portalowner whose default database
   // is the portaldatabase.
   
   sp_addlogin portalowner, portalowner, portaldatabase
   go
   
   // Make this user the owner of portaldatabase.
   
   use portaldatabase
   go
   
   sp_changedbowner portalowner, true
   go
   // Make this user the owner of portalsearchdb
   
   use portalsearchdb
   go
   
   sp_changedbowner portalowner, true
   go
   

2. Update the global.properties.xml DataPool entry:

   <DataPool name="op_portal_ase"
         class="com.onepage.db.DbConnectionBroker"
         driver="com.sybase.jdbc2.jdbc.SybDriver"
         url="jdbc:sybase:Tds:hostname:port?ServiceName=portaldatabase”
         user="dba"
         password="SQL"
         password_encrypted=”false”
         minConnections="1"
         maxConnections="50"
         unusedtimer="360"
         checkouttimer="60"
         reuse="30"
         debug="true" />
   

3. Restart the application server.

Copyright © 2004. Sybase Inc. All rights reserved.

View this book as PDF