Hi Tom:<br><br>It is AG3, the latest release. Thanks for getting back to me and I look forward<br>to AG3.1<br><br>regards,<br><br>west<br><br><div><span class="gmail_quote">On 6/7/07, <b class="gmail_sendername">Thomas D. Uram
</b> <<a href="mailto:turam@mcs.anl.gov">turam@mcs.anl.gov</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi West:<br>
<br>AG2 or AG3?<br><br>AG3 does not have any facility for using a certificate with passphrase,<br>so you should<br>use a VenueServer service certificate to run a VenueServer. The 3.1<br>release will allow<br>you to assign administrative rights to individuals who hold Identity
<br>Certificates, which<br>do require a passphrase.<br><br>So the behavior you're seeing is appropriate to the current AG3 release.<br><br>Tom<br><br><br>On 6/1/07 3:49 PM, west suhanic wrote:<br>> Hello All:<br>>
<br>> There may be a problem with the VenueManager code.<br>><br>> I am running my own VenueServer. In order to run your own VenueServer<br>> you need to generate your own x509 certificates. The problem arises
<br>> when I use a x509 certificate for the VenueServer that requires the user<br>> starting the VenueServer to supply a password. If I use this type of<br>> certificate<br>> the VenueServer starts and operates fine. However when I go to
<br>> configure the<br>> VenueServer using the VenueManager, I cannot connect the VenueManager to<br>> the VenueServer. When I start the VenueManager it prompts me for the<br>> password<br>> for the x509 certificate however it will noyt connect me to the
<br>> VenueServer. If<br>> I use a x509 certificate that does not prompt for a password the<br>> VenueManager works<br>> as expected.<br>><br>> Hopefully someone else can test this scenario to verify my statements.
<br>><br>> regards,<br>><br>> West<br><br></blockquote></div><br>