Multiple Sessions Are Created When You Use Openoffice Tools With A Webdav Connection; Cookie And Session Issues With Nautilus File Manager And Webdav Connections; On A New Install, The Secure Logging Server Is Not Configured Correctly; Communication Problems Between The Novell Audit Client And The Audit Server Might Crash The Linux Access Gateway - Novell ACCESS MANAGER 3.1 SP2 - README 2010 Manual

4.6.14 Multiple Sessions Are Created When You Use OpenOffice Tools with a
WebDAV Connection
When you use OpenOffice Writer and other tools over WebDAV connections, cookies that are set by
the server are not included in requests from the OpenOffice client. As a result, each WebDAV
request from the client creates a new session. If you have limited user sessions, the limit can be
quickly reached, which results in files left in a locked state or with IO errors.
To solve this problem, do not limit user sessions (Devices > Identity Servers > Edit) when users are
using OpenOffice tools over a WebDAV connection.
4.6.15 Cookie and Session Issues with Nautilus File Manager and WebDAV
Connections
The Nautilus File Manager v2.12.2 in SUSE Linux Enterprise Desktop (SLED) 10 SP1 and SP2
does not include cookies when making WebDAV requests. As a result, when the WebDAV server is
accessed through a reverse proxy on the Access Gateway, a new user session is created at the proxy
for every WebDAV request sent from Nautilus. A simple file open can result in the creation of
multiple sessions.
To solve this problem, do not limit user sessions (Devices > Identity Servers > Edit) when users are
making WebDAV requests with the Nautilus File Manager.

4.6.16 On a New Install, the Secure Logging Server Is Not Configured Correctly

The
logevent.conf
the address of the logging server to 127.0.0.1 instead of the IP address specified in the
Administration Console. By default, this address is the IP address of the Administration Console,
but it can be configured for an external auditing server such as a Novell Sentinel server.
To fix the problem:
1 Log in to the Access Gateway as
2 Change to the
3 Open the
LogHost=127.0.0.1
4 Change the IP address to the address of your secure logging server.
5 Reboot the Access Gateway.
4.6.17 Communication Problems between the Novell Audit Client and the Audit
Server Might Crash the Linux Access Gateway
If you have configured your Access Manager system to use a Novell Sentinel or Novell Audit server
for auditing, the Novell Audit client sometimes disconnects from the auditing server. This usually
happens when communication problems exist on the network. When this happens, the Linux Access
Gateway might crash. This issue can also prevent the successful completion of any Linux Access
Gateway configuration changes.
To solve this problem, make sure that no communication problems exist between the auditing client
on the Linux Access Gateway and the auditing server.
22 Novell Access Manager 3.1 SP2 Readme
file, which controls the configuration for the secure logging server, initializes
root
directory
/etc
file and find the following line:
logevent.conf
.