See Installation, specifically …Create a file called Duo_org.ps1… Integration key, Secret key, and API hostname - these are needed later to configure the Duo-PSModule in Azure Automation.īefore saving the application, check the boxes for Grant read resource and Grant write resource (or whatever permissions your use case requires):ĭuo authentication settings for Duo-PSModule in Azure AutomationĪs noted, Duo_org.ps1 usually holds the Duo Admin API connection and authentication information (created above). Select Applications -> Protect an Application -> Type “ Admin API” and click Protect. Creating the Duo Admin API application and granting permissionsįor the Duo-PSModule to connect and interact with a Duo implementation, the Duo Admin API must be exposed by creating a new Application of type “Admin API” in the Duo Console. If you prefer not to include a blank Duo_org.ps1, you can also update the source code of Duo.psd1, removing references to Duo_org.ps1 here, here, and here. The final contents of Duo.zip should reflect the following:Īt this point, the module can be successfully added (imported) into an Azure Automation account:Īnother option (instead of adding a blank Duo_org.ps1 file) In Azure Automation, there is a better way (more on that later). With the Duo-PSModule installed locally, Duo_org.ps1 provides authentication parameters (Duo integration key, secret key, API hostname, etc.). For me, the path of least resistance was adding a blank Duo_org.ps1 file to my Duo.zip archive. Verify that a valid value is specified for thisįield in the 'C:\Users\Client\Temp\XXXXXXXXXX\Duo\Duo.psd1' file. Manifest is not valid: Cannot find path 'C:\Users\Client\Temp\XXXXXXXXXX\Duo\Duo_org.ps1'īecause it does not exist. Internal error message: The member 'ScriptsToProcess' in the module While importing the module, an error occurred while processing the moduleĬontent. As a result, importing the correctly structured zip file into an Azure Automation account will fail as follows: Error importing the module Duo. The module (specifically Duo.psd1) has several references to the “ Duo_org.ps1” file, which by design, does not exist in the GitHub repository (or downloaded zip file). In the case of the Duo-PSModule, that is not enough. I created a new zip file called Duo.zip and added the module files from the GitHub zip archive to the root accordingly: This is an easy fix - the module files ( Duo.psm1 and Duo.psd1) must be at the root of the zip file, and the name of the zip file must match the name of the module. :Ĭannot import the module of name Duo-PSModule-master, as the module The error message resulting from doing so is: Error importing the module Duo-PSModule-master. Importing the Duo-PSModuleĪdding the Duo PowerShell module to an Azure Automation account is not as easy as downloading the zipped version from GitHub and uploading it into Azure Automation. I am a big fan of this module and have used it previously - see this post. It is a robust Power Shell wrapper for the Duo Admin API. In this post, I will describe the process and best practices for importing and using the Duo-PSModule PowerShell module in Azure Automation. Since I am a “PowerSheller” already, the learning curve is minimal. The allure for me is PowerShell RunBooks. All product names, logos, and brands used in this post are property of their respective owners.Īs of late, I’ve been spending time in Azure Automation intending to reclaim parts of my day from recurring (sometimes mundane) tasks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |