pegasus/Attic/readme.html - diff

Return to readme.html CVS log

Up to [Pegasus] / pegasus / Attic

Diff for /pegasus/Attic/readme.html between version 1.3 and 1.5

version 1.3, 2004/03/09 21:38:27

version 1.5, 2004/03/10 19:24:13

Line 13

PEP #: 103

Title: OpenPegasus Version 2.3

Release Readme file

Version: 1.0

Version: 1.1

Created: 12 November 2003

Authors: Karl Schopmeyer

Authors: Karl Schopmeyer, Konrad Rzeszutek

Status:  draft

Version History:

<table border="1" cellspacing="1" bordercolordark="#666666"

Line 34

<td>Update from 2.2 Release notes. Converted to HTML</td>

</tr>

<tr>

<td align="center">March 10 2004</td>

<td align="center">Konrad Rzeszutek</td>

<td>Added sections describing SSL and PAM configuration</td>

</tr>

<tr>

Line 108

Line 114

<a href="#Commands">Commands</a>

<a href="#Creating SSL certifications">Creating SSL certifications</a>.

<a href="#Creating SSL certifications">Creating SSL certifications</a>

<a href="#Configuring SSL">Configuring Pegasus to use SSL</a>.

<a href="#Configuring SSL">Configuring Pegasus to use SSL</a>

<a href="#Configuring PAM">Configuring Pegasus to use PAM</a>

<a href="#Testing with ICU enabled">Testing with ICU enabled </a>

Line 875

Line 884

before embarking on this endeavour.

To configure Pegasus to take advantage of SSL, configure

cimserver_planned.conf to have:

CIMServer to have the following configuration options set to:

sslTrustFilePath=client.pem

sslCertificateFilePath=server.pem

Line 883

Line 892

httpsPort=5989

enableHttpsConnection=true

</pre></blockquote>

using the cimconfig utility:

cimconfig -p -s enableHttpsConnection=true

</pre></blockquote>

(The client.pem and server.pem are the certifications

files created per the steps in the earlier section).

For good riddance you might consider closing down

the cleartext 5988 port. Modify your cimserver_planned.conf

the cleartext 5988 port. Modify your CIMServer configuration

to include:

enableHttpConnection=false

</pre></blockquote><h1><a name="Testing with ICU enabled">Testing with ICU enabled</a></h1>

</pre></blockquote>

using cimconfig.

<h1><a name="Configuring PAM">Configuring Pegasus to use PAM</a></h1>

In order to use PAM Authentication you have to compile Pegasus

with one extra enviroment flags:

PEGASUS_PAM_AUTHENTICATION=1

</blockquote></pre>

You can also set the PEGASUS_ALWAYS_USE_PAM=1 flag to disable

Pegasus password authentication using a flag text-file (recommended).

After compiling (refer to section <a href="#Building Pegasus">Building Pegasus </a>

for details), follow these two important steps:

<ul>

<ul>a). Copy the rpm/wbem file in-to /etc/pam.d directory.

This notifies PAM what kind of libraries to use when authenticating

Pegasus.</uL>

<ul>

b). Modify CIMServer configuration options:

usePAMAuthentication=true

enableAuthentication=true

</blockquote></pre>

And if you want to allow 'root' to login (*not recommended*)

enableRemotePrivilegedUserAccess=true

</blockquote></pre>

using the cimconfig utility, such as:

cimconfig -p -s usePAMAuthentication=true

</pre></blockquote>

</ul>

The user is authenticated using HTTP Basic method, thererfore it is

strongly suggested you use SSL connection instead of normal HTTP connection.

Refer to section

<a href="#Configuring SSL">Configuring Pegasus to use SSL</a> for more details on creating and using SSL keys.

<h1><a name="Testing with ICU enabled">Testing with ICU enabled</a></h1>

ICU (International Components for Unicode) refers to the set of libraries that

Pegasus uses to run globalized. For example: these libraries are used to

load messages in different languages, format currency and numbers according to

Legend:

Removed from v.1.3
changed lines
	Added in v.1.5

No CVS admin address has been configured