Yubico Forum

I do apreciate the upgrades for this server, but the upgrade process is a pain....
creating a second machine, running the script, swapping IP addresses, deleting the old appliance.
Not mentioning the problems with virtual machine names not allowed to be duplicate in vSphere.

Surely an 'in-place' upgrade for the virtual appliance should not be difficult to implement by Yubico.
I kindly request that Yubico plan for this feature.

any seconds ?

Hi there,

We have upgrades through packages on the road-map but near-term the upgrade the procedure is similar way to how they are performed today. However, we are open for smaller changes to improve the process and make it easier to upgrade.

Please tell us if you have any suggestions on how you would simplify this and any other input which could be useful to us.

Tom.

_________________
-Tom

well, simply put, I would like to see that the Yubiradius server parts (scripts, PHP, etc) are distributed in a debian compliant repository.
The virtual appliance should be distributed with the repository in its sources.lst
A simple :

apt-get update && apt-get upgrade

should take care of there entire upgrade process, not only for Apache, Webmin, etc, but also for the Yubiradius software.

I noticed there is a Yubiradius repository in the sources.lst, since it throws an error when I do : apt-get update

Obviously apt-get update does not correct the problem.

Please see following steps to migrate YRVA 3.0 to YRVA 3.6.1:

The migration scrips are available from Version 3.1.

We have the latest version of YubiRADIUS v3.6.1 with more features.

You can use latest version of YubiRADIUS version 3.6.1, download the latest VM from http://www.yubico.com/products/services ... ubiradius/

To start working with YubiRADIUS 3.6.1 with 3.0 data, you have to follow the steps given below:

1. If you have configured the local validation server please import the YubiKey's AES key secret to YRVA3.6.1 instance (.csv file created by personalization tool)

2. You have to take a database dump of "ykmap" table from YRVA3.0 and import to the YRVA3.6.1 database "ykmap" table

3. Create the domain in YRAV3.6.1 instance and configure the "user import" to your "AD/LDAP" to import the users.

4. Create the radius client configuration in YRVA3.6.1 as per YRVA 3.0 setup.

5. Make "Auto Provisioning" enable in "Global Configuration" as well as Domain "Configuration"

6. Make "Validation Server" settings as "Local Validation Server" or "YubiCloud Validation Server" accordingly in YRVA3.6.1

Also, please refer the YubiRADIUS configuration guide available at http://static.yubico.com/var/uploads/pd ... 5_3_v1.pdf

_________________
-Tom