AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080922103502.1904df8f@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<sripal.surendiran@onstor.com>,<eric.barrett@onstor.com>,<acooke@css.glasshouse.com>,<dl-cstech@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	48D7B0E2.4010806@onstor.com
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 22 Sep 2008 10:35:21 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Sripal <sripal.surendiran@onstor.com>
Cc: Eric Barrett <eric.barrett@onstor.com>, "Alan Cooke (Glasshouse)"
 <acooke@css.glasshouse.com>, dl-cstech <dl-cstech@onstor.com>
Subject: Re: GUI certificate for release 3.1.1.0 - case 9716
Message-ID: <20080922103521.5fd278f0@ripper.onstor.net>
In-Reply-To: <48D7B0E2.4010806@onstor.com>
References: <BB375AF679D4A34E9CA8DFA650E2B04E0BAC88A2@onstor-exch02.onstor.net>
	<48D7B0E2.4010806@onstor.com>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, 22 Sep 2008 20:21:14 +0530 Sripal
<sripal.surendiran@onstor.com> wrote:

> Hi Alan,
>=20
> The procedure mentioned in the wiki page describes about how to
> create a self-signed SSL certificate. I am not sure if the customer
> wants to have a third party signed SSL certificate (like verisign) or
> their certificate has been expired. SSL certificate has been renewed
> for another one year in 3.1.1.3
>=20
> -Sripal

Sounds like they just need to upgrade.

> Eric Barrett wrote:
> > Alan,
> > Making a CSR is a fairly arcane process. I don't think we have any=20
> > documented method for doing so.
> > (What they're trying to do is make it so they can access the WebUI=20
> > without browser warnings; they may have a site-wide policy
> > prohibiting them from accessing any page not so configured.)
> > Unless somebody corrects me, this isn't supported. They'll just
> > have to configure an exception for the Bobcats.
> > -E
> >
> > ------------------------------------------------------------------------
> > *From:* Alan Cooke (Glasshouse)
> > *Sent:* Monday, September 22, 2008 9:35 AM
> > *To:* dl-cstech
> > *Subject:* GUI certificate for release 3.1.1.0 - case 9716
> >
> > Hi All,
> >
> > Have customer British Energy asking about the GUI certificate for=20
> > their systems running 3.1.1.0. They say in case 9716:
> >
> > =E2=80=9Cwe need to generate a Certificate Signing Request (CSR) for ou=
r=20
> > 2260's so that they have a valid (in-date) certificate for the
> > WebUI.=E2=80=9D
> >
> > Do they mean the Secure Sockets Layer certificate as discussed last=20
> > year by Ben and Charissa?
> >
> > Do Onstor do this or would this be done by the customer? This is a=20
> > secure site so they may prefer to do it themselves.
> >
> > I have looked on the Onstor wiki page and that says about creating
> > an SSL =E2=80=9CLogin to your compile2 machine and follow the procedure
> > mentioned below for creating the SSL certificate.=E2=80=9D
> >
> > If the customer was doing this could they just load the OpenSSL
> > from the download site http://www.openssl.org/source files onto
> > their Bobcat and run it from there?
> >
> > Any info appreciated.
> >
> > Regards =E2=80=A6 Alan.
> >
>=20
