Configure an ADFS Stamp

HOST VM

On AzS Development Kits, sign in to the physical host.

On multi-node integrated systems, the host must be a system that can access the privileged endpoint.

Prerequisite - Active Directory module for Windows PowerShell:

In Windows Server 2019/2016/2012 R2, you can install the Active Directory module for Windows PowerShell from the Server Manager graphical console using the Add Roles and Features Wizard. Start the wizard and at the stage of selecting features you need to select the item Remote Server Administration Tools > Role Administration Tools > AD DS and AD LDS Tools > Active Directory module for Windows PowerShell.

Steps:

Place the RegisterVConnectAdminApp.ps1 file in a temp folder. [This file can be found in the install folder of Host VM where VConnect RP was installed: c:\CloudAssert\VConnectMSM\AppRegistration\]
Open a new elevated (administrative) PowerShell console and change to the above directory. Use a new window to avoid problems that might arise from incorrect Power Shell modules that are already loaded on the system
Run the RegisterVConnectAdminApp.ps1 script with appropriate parameters

.\RegisterVConnectAdminApp.ps1 -ServiceAdminUser '' -AzureStackAdminResourceManagerEndpoint '' -AzureDirectoryTenantId '' -AzureEnvironment 'AzureCloud' -IdentitySystemType 'ADFS' -PrivilegedEndpoint '192.168.200.224' -CloudAdminUser '' -adminSubscriptionId ''

Eg:
.\RegisterVConnectAdminApp.ps1 -ServiceAdminUser 'msmtest@cloudassertrp.contoso.com' -AzureStackAdminResourceManagerEndpoint 'https://adminmanagement.local.contoso.com' -AzureDirectoryTenantId  'eef3d6b3-cf97-42c1-9cc5-f68905cdd1a6' -AzureEnvironment 'AzureCloud' -IdentitySystemType 'ADFS' - PrivilegedEndpoint ‘191.168.200.224’ -CloudAdminUser 'cloudadmin@azurestack.local' -adminSubscriptionId 'a7f2bc5b-2287-4a8b-b256-dcb14dd06878'

The script outputs VConnectRegistrationOutput.txt in the same AppRegistration folder having all the information needed to add a new azure stack connection in VConnect coming up next.

VConnect Resource Provider VM

To support certificate authentication, import the .pfx file generated in the above step into VConnect Resource Provider VM. Ensure the certificate is imported into the Personal store of this VM.

Once imported follow below steps to give appropriate permissions:

Open the certificate console (Using MMC) in the VConnect VM.
Go to Personal -> On the imported certificate, Right click -> Select All Tasks, and then click Manage Private Keys.
In the new window, click Add.
Under 'Enter object name to select' type IIS_IUSRS and click OK.
In the previous window, click Apply, and then OK to close the window

VCONNECT ADMIN EXTENSION

Create a new connection from the VConnect admin extension in the admin portal.

Go to the admin portal of the master stamp where VConnect RP is deployed
Go to All Services → VConnect → Connections → Azure Stack Hub
Click on Add button to create new connection.

Basic Settings

Use the VConnectRegistrationOutput.txt file to fill in details, screenshots below for reference.

Offline Repository Details

Offline Repository settings in connection page allows operator to use different for a single stamp.

"Offline Repository Details" settings will be visible only when Offline Marketplace Download settings is configured.

Remote PowerShell Machine details

For each connection, separate remote PowerShell machine can be set to the global setting (VConnect → Settings → Azure Stack Hub - Remote PowerShell Settings) can be used. This needs to be configured when the Azure Stack Hub stamp has different Az PowerShell module version or if there is a VPN dependency

"Remote PowerShell Machine" settings will be visible only when Offline Marketplace Download settings is configured.