johlju

PROMPT: Jag vill använda en Identity Provider för att autentisera och få åtkomst till en on-premises PowerBI Reporting Services. Hur ska man göra konfigurationen för PowerBI Reporting Services för att kunna autentisera mot en Identity Provider?

För att konfigurera Power BI Reporting Services (on-premises) att autentisera mot en Identity Provider behöver du implementera en anpassad säkerhetsförlängning (custom security extension). Som standard använder Reporting Services Windows-autentisering, men genom att skapa en anpassad säkerhetsförlängning kan du integrera andra autentiseringsmetoder, inklusive externa Identity Providers.

Här är stegen för att göra detta:

1. Förstå Kraven: Se till att din Identity Provider stöder standardautentiseringsprotokoll som SAML, OAuth eller OpenID Connect.

2. Utveckla en Anpassad Säkerhetsförlängning:

• Skapa en .NET-assembly som implementerar IAuthenticationExtension-gränssnittet från Reporting Services.

johlju

# Innehållet i $b ska ersätta raden "#placeholder parameters" i innehållet av $a.
# Men saker får fnatt som man kan se i result.txt och den verkar "loopa" och göra help knasiga saker.
# Testat i PS7.4.1 enbart.
# Löste det genom att istället använda [RegEx]::Replace(), men vore roligt att veta varför.

$a = @'
# Version v#.#.# (yyyy-MM-dd)

#placeholder parameters

johlju

# Prerequisites:
#
# Install Azure CLI: https://docs.microsoft.com/en-us/cli/azure/install-azure-cli
winget install --id Microsoft.AzureCLI
# restart console prompt
# Install AzureDevOps extension
az extension add --name azure-devops
# Install 1Password CLI: https://developer.1password.com/docs/cli/get-started
winget install 1password-cli
# restart console prompt

johlju

class PSResourceObject : IComparable, System.IEquatable[Object]
{
    [System.String]
    $Name

    [System.Version]
    $Version

    [System.String]
    $PreRelease

johlju

# Install Azure CLI: https://docs.microsoft.com/en-us/cli/azure/install-azure-cli
# Install AzureDevOps extension: az extension add --name azure-devops
# Login with the account that access DSC Community pipelines: az login --allow-no-subscriptions
# Run this script and pass the PAT in the parameter.

[CmdletBinding()]
param
(
    # TODO: Fix as PSCredential so that PAT is not part of PowerShell command line history
    [Parameter(Mandatory = $true)]

johlju

# For some attempts
using module SqlServerDsc

$ConfigurationData = @{
    AllNodes = @(
        @{
            NodeName = 'localhost'
            PSDscAllowDomainUser = $true 
            PSDSCAllowPlainTextPassword = $true
        }

johlju

Steps to rename a DSC Community module repository

GitHub repository, Azure Devops and PowerShell Gallery

1. Send in a PR (and merge it) to update the pipelines files so the repo are using the latest from Sampler.

   ./build.ps1 -ResolveDependency -Tasks build
   # Use the default values and answer Y on all questions 
   New-SampleModule -DestinationPath '..\' -ModuleType 'dsccommunity' -ModuleAuthor 'DSC Community contributors' -ModuleName (Split-Path -Leaf $PWD) -ModuleDescription 'no description' -LicenseType MIT -SourceDirectory 'source' -ModuleVersion '0.0.1' 
   Get-ChildItem -Path *.bak -Recurse -Force | Remove-Item -Force
   

johlju

<#

Source:

    SourceLineNumber HitCount
    ---------------- --------
                20      219
                22      219
                22      219
                22      219

johlju

BeforeAll {
    Remove-Module -Name 'DscResource.Common' -Force
    New-Module -Name 'DscResource.Common' -ScriptBlock {
        function Assert-Module
        {
            [CmdletBinding()]
            param
            (
                [Parameter(Mandatory = $true)]
                [System.String]

johlju

* Should -Throw has a breaking change that it is no longer using `-contains` but instead `-like`

Expected an exception, with message 'Robocopy reported errors when copying files. Error code: 8.' to be thrown, but the message was 'System.InvalidOperationException: Robocopy reported errors when copying files. Error code: 8. (SQLCOMMON0012)'.
Solution, wasn't using the localized string (used hard-coded string) and then needed to use test helper Get-InvalidOperationRecord to get the correct string that contains System.InvalidOperationException (alternative is to use wildcards *)

Assert-MockCalled -> Should -Invoke (uses the same parameters, so backward compatible)

InModuleScope must be inside Describe-block.
Use it where it is needed, for example using localization variable.