v2.0.0
Universal Dashboard is now a part of PowerShell Universal. This documentation is for reference to the v2 version of Universal Dashboard and is no longer maintained. PowerShell Universal Documentation can be found here.
v2.0.0
v2.0.0
Released: August 31st, 2018
New Features
Community Edition
Universal Dashboard Community Edition is now available on the Gallery. This free and open-source version of Universal Dashboard has no time limits and can be used to create beautiful websites and REST APIs without paying a licensing cost.
1
Install-Module UniversalDashboard.Community
Copied!
Enterprise Edition
Universal Dashboard Enterprise Edition builds on top of what's available in Community Edition but extends the platform to enable authentication, authorization and branding support.
1
Install-Module UniversalDashboard
Copied!
Tree View
A tree view control has been added to allow you to expose and navigate tree structures in UD. You can hook into PSProviders and handle click events to display data.
Floating Action Button
A floating action button is a button pinned to the bottom right of the page. It allows you to put some simple, easy to access controls on your dashboard. They support nested buttons and onClick event handlers.
More Customizable Toasts
In previous versions of UD, you could send toast messages view Send-UDToast. In 2.0, you can now create extremely customized toast messages that allow you to configure colors, text size, icons and timing. Using Show-UDToast and Hide-UDToast you have total control over the toast messages.
Publish Folders
There was no good way to serve any old file in previous versions of Universal Dashboard. The newly added Publish-UDFolder cmdlet enables just that. You can now publish any folder you'd like and assign a URL to it.
1
Start-UDRestApi -Port 10001 -PublishedFolder @(
2
Publish-UDFolder -Path $TempPath -RequestPath "/temp"
3
)
4
Invoke-WebRequest http://localhost:10001/temp/myFile.txt
Copied!
Improved Endpoint Initialization
Up until this version of you would use the EndpointInitializationScript to setup the endpoints for UD components. The ScriptBlock was converted into a string and wasn't a good way to actually initialize the endpoints. It made it difficult to import modules, load function and variables into endpoints.
With 2.0, you can now use the New-UDEndpointInitialization cmdlet to create an InitialSessionState object. This object is used to initialize all the runspaces used within UD. This is a standard PowerShell object and can be used to add modules, variables and functions to the runspaces.
1
$Initialization = New-UDEndpointInitialization -Module MyModule -Variable "MyVariable" -Function 'Get-Stuff'
2
​
3
$dashboard = New-UDDashboard -Title "Test" -Content {
4
New-UDCounter -Title "Counter" -Id "Counter" -Endpoint {
5
# Function exported from MyModule
6
Get-Number
7
}
8
​
9
New-UDElement -tag "div" -Id "variable" -Content {
10
$MyVariable
11
}
12
​
13
New-UDElement -tag "div" -Id "function" -Content {
14
Get-Stuff
15
}
16
} -EndpointInitialization $Initialization
Copied!
Improved Endpoint Arguments
In previous versions of Universal Dashboard, variables were "automatically" added to Endpoints based on the local scope. This meant that you didn't really have to do anything to get variables into an endpoint. It didn't work very well all the time. :( Although this automatic import is still happening, you now have more control over endpoints. You can now use
New-UDEndpoint and a handy new -ArgumentList parameter to pass in values to your endpoints.This will work for event handlers as well as controls with Endpoint callbacks.
1
$Name = "calc"
2
New-UDButton -Text 'Start Calc' -Id 'button' -OnClick (
3
New-UDEndpoint -Endpoint { Start-Process $ArgumentList[0] } -ArgumentList $Name
4
)
Copied!
Role-Based Access (Enterprise Only)
Universal Dashboard has offered authentication for a few versions now via login pages and JSON Web Tokens. In this version we are now introducing authorization. The first type of authorization that you can utilize is role-based access. You can assigning roles to pages and REST API endpoints to allow only certain roles access to those pages or endpoints. Pages that aren't accessible won't even show up in the navigation menu.
When a user logs in, you can assign roles to that user. In the below example, Adam is assigned the Admin role on login. The Home and Settings pages allow Admins to access them while only Users cannot access the Settings page.
1
$AuthenticationMethod = New-UDAuthenticationMethod -Endpoint {
2
param([PSCredential]$Credential)
3
​
4
elseif ($Credential.UserName -eq "Adam") {
5
New-UDAuthenticationResult -UserName "Adam" -Success -Role "Admin"
6
} else {
7
New-UDAuthenticationResult -ErrorMessage "You're not Adam!!"
8
}
9
}
10
​
11
$LoginPage = New-UDLoginPage -AuthenticationMethod $AuthenticationMethod
12
​
13
$dashboard = New-UDDashboard -Title "Test" -LoginPage $LoginPage -Pages @(
14
New-UDPage -Name "Home" -Content {
15
New-UDHeading -Text "Home" -Id "Home"
16
} -AuthorizedRole @("User", "Admin")
17
​
18
New-UDPage -Name "Settings" -Content {
19
New-UDHeading -Text "Settings" -Id "Settings"
20
​
21
New-UDElement -Tag "div" -Id "myEndpoint" -Endpoint {
22
"Test"
23
}
24
} -AuthorizedRole "Admin"
25
)
Copied!
Policy-Based Authorization (Enterprise Only)
In addition to role-based authorization, you can also use policy-based authorization. Policy authorization allows you to evaluate a user's claims and decide whether the user has access to a particualr page or endpoint.
Policy-based authorization works well for 3rd party authentication mechanisms. You can check claims provided by services such as Azure Active Directory. This means you don't need to update a dashboard to change the access of users to the dashboard.
In the below example, the policy is checks to see if the user has a groups claim with a value of administrators. If they as part of this group, they have access to the setting page.
1
$AuthorizationPolicy = New-UDAuthorizationPolicy -Name "Policy" -Endpoint {
2
param($User)
3
​
4
$User.HasClaim("groups", "administrators")
5
}
6
​
7
$LoginPage = New-UDLoginPage -AuthenticationMethod $AuthenticationMethod -AuthorizationPolicy @($AuthorizationPolicy)
8
​
9
$dashboard = New-UDDashboard -Title "Test" -LoginPage $LoginPage -Pages @(
10
New-UDPage -Name "Home" -Content {
11
New-UDHeading -Text "Home" -Id "Home"
12
}
13
​
14
New-UDPage -Name "Settings" -Content {
15
New-UDHeading -Text "Settings" -Id "Settings"
16
​
17
New-UDElement -Tag "div" -Id "myEndpoint" -Endpoint {
18
"Test"
19
}
20
} -AuthorizationPolicy "Policy"
21
)
Copied!
Azure Active Directory Authentication (Enterprise Only)
New-UDAuthenticationMechanism now supports configuring Azure Active Directory Authentication. Paired with policy-based authentication, you can assign users to groups that have access to particular pages and endpoints within Universal Dashboard.
Breaking Changes
System Requirements
UD has been upgraded to use ASP.NET 2.1. Because of this the following system requirements are necessary for UD 2.0.
Window PowerShell
- PowerShell v5.1
- .NET 4.7.1
PowerShell Core
- PowerShell Core v6.1
DebugEndpoint Parameter Removed
The
-DebugEndpoint parameter has been removed. Guidance is to use Wait-Debugger within Endpoints for debugging.EndpointInitializationScript Parameter Removed
The
-EndpointInitializationScript parameter has been removed from New-UDDashboard cmdlet. It is suggested to use the New-UDEndpointInitialization cmdlet instead.DateTimeFormat Parameter of New-UDTable
The
-DateTimeFormat parameter has been moved from New-UDTable to Out-UDTableData.Send-UDToast renamed to Show-UDToast
With the addition of Hide-UDToast, it made sense to rename Send-UDToast to Show-UDToast.
Issues Resolved
Last modified 2yr ago
Copy link