Can't use non-default Keystone ADMIN_TOKEN when installing SDN Controller 2.3.5 version

[Bansheezm]

Hi all.

HP VAN SDN Controller has been releases recenlty and I wanted to give it a try.

I have Ubuntu 14.04 LTS and my own Keystone service from OpenStack Icehouse release - 1:2014.1.1.

I follow steps from this installation guide.

Before actualy installing hp-sdn-ctl_2.3.5.6505_amd64.deb with dpkg I set up environment variable ADMIN_TOKEN, because my keystone is set up to use non default (ADMIN) value. All tenants and users and user-roles are already created in my keystone by hand. 

# export ADMIN_TOKEN=SomeAdmin_token_ratherLongString

I am coping token from keystone.conf to be sure it is correct.

After that I

# dpkg -i hp-sdn-ctl_2.3.5.6505_amd64.deb

and get 

(Reading database ... 22709 files and directories currently installed.)
Unpacking hp-sdn-ctl (from hp-sdn-ctl_2.3.5.6505_amd64.deb) ...
Setup has detected a compatible jre-headless - 1.7.0_55
Verifying keystone server...
Unable to validate keystone at http://127.0.0.1:35357/v2.0 - Invalid administrator token [ ADMIN ] - Unauthorized
Halting installation !!

Looks like installation is not using my custom ADMIN_TOKEN set from evironment variables and using value ADMIN instead. How can I overcome this? I really don't want to use default ADMIN value.

[Gerhard Roets · Accepted solution]

Hi Bansheezm

Try the variable AUTH_TOKEN instead of ADMIN_TOKEN.

Kind Regards
Gerhard

HP SDN Team

[Bansheezm]

This helped. Thank you.