PaloAltoNetworks / panhandler

Panhandler is a tool to manage config snippets and Skillets for PAN-OS devices
Apache License 2.0
41 stars 19 forks source link

Azure Authorization Token Error - Prisma Access Skillet #212

Closed suspenceiskillinu closed 4 years ago

suspenceiskillinu commented 4 years ago

When attempting to run the Prisma Access Deploy Panorama skillet for Azure, specifically, I run into an error during the plan stage.

Expected behavior

As I am authenticating via login token in a prior step from the browser of the OS hosting the Panhandler docker image, it should be able to reference the successful login during the planning stage.

Current behavior

The following error is shown:

Error: Error running plan: 1 error(s) occurred:

Possible solution

I am not sure what I am missing. I have another machine (LIAB) that is able to perform the plan steps just fine. I am assuming that the docker image may have the ability to reference the Azure token on the base OS, perhaps? Maybe I am missing that on my other builds. If so, I don't see that documented anywhere.

Steps to reproduce with screenshots

  1. Run the Prisma Access Deploy Panorama skillet from Panhandler and log in from the OS browser where the docker image resides.

image

  1. Enter credentials and other specifics (i.e. resource group name) to deploy in Azure (validate, init, and apply)
  2. Validate is successful
  3. Plan error

image

Context

I am simply testing the skillet.

Your Environment

This works in the standard LIAB for SEs without issue. I am trying to replicate in Mac OS (Catalina 15.5.5) and Ubuntu 18.04. I deploy Panhandler via curl without any custom parameters.

welcome[bot] commented 4 years ago

:tada: Thanks for opening your first issue here! Welcome to the community!

suspenceiskillinu commented 4 years ago

FYI, I also posted this directly to the Prisma Access Skillets repo in case that is a better location for this issue.

nembery commented 4 years ago

Thanks for the report. New build is incoming with the required deps

nembery commented 4 years ago

Build is complete and should be good to go. Running the installer script again will pull the latest image, which should resolve this problem

suspenceiskillinu commented 4 years ago

Yep that worked for me :).

nembery commented 4 years ago

👍