SD-WAN

 View Only
last person joined: 3 days ago 

Forum to discuss HPE Aruba EdgeConnect SD-WAN and SD-Branch solutions. This includes SD-WAN Orchestration WAN edge network functions - routing, security, zone-based firewall, segmentation and WAN optimization, micro-branch solutions, best practics, and third-party integrations. All things SD-WAN!
Back to discussions
Expand all | Collapse all

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

This thread has been viewed 0 times

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

    Posted Aug 14, 2014 08:51 AM

    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.

     


    #keystone
    #installation
    #SDN


  • 2.  RE: Can't use non-default Keystone ADMIN_TOKEN when installing SDN Controller 2.3.5 version

    Posted Aug 14, 2014 09:15 AM

    Hi Bansheezm

     

    Try the variable AUTH_TOKEN instead of ADMIN_TOKEN.

     

    Kind Regards
    Gerhard

    HP SDN Team



  • 3.  RE: Can't use non-default Keystone ADMIN_TOKEN when installing SDN Controller 2.3.5 version

    Posted Aug 14, 2014 09:57 AM
    This helped. Thank you.