Skip to content

Releases: CGI-FR/IoT-Hub-Portal

v2.8.0-rc0

12 Aug 08:51
5edbd1a
Compare
Choose a tag to compare
v2.8.0-rc0 Pre-release
Pre-release

What's Changed

Breaking changes

N/A

New Features

Bug fixes

Minor Changes

  • Fix #969 - Refactor LoRa Device model and LoRaDevice classes by @kbeaugrand in #1056
  • Bump FluentValidation from 11.1.0 to 11.1.1 in /src by @dependabot in #1041
  • Bump Hellang.Middleware.ProblemDetails from 6.4.2 to 6.5.0 in /src by @dependabot in #1047
  • Bump Microsoft.AspNetCore.Components.WebAssembly.Authentication from 6.0.7 to 6.0.8 in /src by @dependabot in #1052
  • Bump FluentValidation from 11.1.1 to 11.2.0 in /src by @dependabot in #1051
  • Bump Microsoft.AspNetCore.Components.WebAssembly.Server from 6.0.7 to 6.0.8 in /src by @dependabot in #1053
  • Bump Microsoft.AspNetCore.Authentication.OpenIdConnect from 6.0.7 to 6.0.8 in /src by @dependabot in #1050
  • Bump Hellang.Middleware.ProblemDetails from 6.5.0 to 6.5.1 in /src by @dependabot in #1057
  • Bump Microsoft.Extensions.Http.Polly from 6.0.7 to 6.0.8 in /src by @dependabot in #1055
  • Bump Microsoft.AspNetCore.Mvc.Testing from 6.0.7 to 6.0.8 in /src by @dependabot in #1054
  • Bump Microsoft.AspNetCore.Authentication.JwtBearer from 6.0.7 to 6.0.8 in /src by @dependabot in #1058
  • Bump Microsoft.AspNetCore.Components.WebAssembly from 6.0.7 to 6.0.8 in /src by @dependabot in #1049
  • Bump Microsoft.AspNetCore.Components.WebAssembly.DevServer from 6.0.7 to 6.0.8 in /src by @dependabot in #1048
  • Bump Microsoft.NET.Test.Sdk from 17.2.0 to 17.3.0 in /src by @dependabot in #1071
  • Bump actions/setup-python from 2 to 4 by @dependabot in #1072

Full Changelog: v2.7.0...v2.8.0-rc0

v2.7.1

10 Aug 09:42
Compare
Choose a tag to compare

What's Changed

Breaking changes

N/A

New Features

  • Add configurable API version support for LoRaWAN Management function by @kbeaugrand in 622db99

Minor changes

Full Changelog: main...hotfix/2.7

v2.7.0

08 Aug 07:18
72436d5
Compare
Choose a tag to compare

What's Changed

Breaking changes

N/A

New Features

Bug Fixes

Minor Changes

  • Bump MudBlazor from 6.0.13 to 6.0.14 in /src by @dependabot in #1003
  • Bump xunit.extensibility.core from 2.4.1 to 2.4.2 in /src by @dependabot in #1015
  • Bump xunit.extensibility.execution from 2.4.1 to 2.4.2 in /src by @dependabot in #1016
  • Bump Moq from 4.18.1 to 4.18.2 in /src by @dependabot in #1024
  • Bump Microsoft.Azure.Devices.Shared from 1.30.1 to 1.30.2 in /src by @dependabot in #1026
  • Bump Microsoft.Azure.Devices from 1.37.1 to 1.38.0 in /src by @dependabot in #1025
  • Bump Microsoft.Azure.Devices.Provisioning.Service from 1.18.1 to 1.18.2 in /src by @dependabot in #1023
  • Bump docker/build-push-action from 3.1.0 to 3.1.1 by @dependabot in #1034

Full Changelog: v2.6.0...v2.7.0

v2.6.0

03 Aug 13:27
81863e6
Compare
Choose a tag to compare

What's Changed

Breaking Changes

N/A

New Features

Bug Fixes

Minor Changes

Full Changelog: v2.5.0...v2.6.0

v2.5.0

22 Jul 13:23
2981b3d
Compare
Choose a tag to compare

What's Changed

Braking Changes

  • App EUI field has been moved from LoRaWAN Device model to LoRa WAN device (API changes)

New features

Bug fixes

Refactoring

Minor Changes

  • Bump MudBlazor from 6.0.10 to 6.0.11 in /src by @dependabot in #902
  • Bump Microsoft.Graph from 4.33.0 to 4.34.0 in /src by @dependabot in #903
  • Bump Azure.Data.Tables from 12.6.0 to 12.6.1 in /src by @dependabot in #909
  • Bump Azure.Storage.Blobs from 12.12.0 to 12.13.0 in /src by @dependabot in #908
  • Bump Microsoft.AspNetCore.Components.WebAssembly from 6.0.6 to 6.0.7 in /src by @dependabot in #922
  • Bump Microsoft.Extensions.Http.Polly from 6.0.6 to 6.0.7 in /src by @dependabot in #921
  • Bump Microsoft.AspNetCore.Components.WebAssembly.Server from 6.0.6 to 6.0.7 in /src by @dependabot in #920
  • Bump Microsoft.AspNetCore.Mvc.Testing from 6.0.6 to 6.0.7 in /src by @dependabot in #923
  • Bump Microsoft.AspNetCore.Components.WebAssembly.DevServer from 6.0.6 to 6.0.7 in /src by @dependabot in #925
  • Bump Microsoft.AspNetCore.Components.WebAssembly.Authentication from 6.0.6 to 6.0.7 in /src by @dependabot in #919
  • Bump Microsoft.AspNetCore.Authentication.JwtBearer from 6.0.6 to 6.0.7 in /src by @dependabot in #924
  • Bump Microsoft.AspNetCore.Authentication.OpenIdConnect from 6.0.6 to 6.0.7 in /src by @dependabot in #926
  • Bump Swashbuckle.AspNetCore from 6.3.1 to 6.3.2 in /src by @dependabot in #928
  • Bump MudBlazor from 6.0.11 to 6.0.12 in /src by @dependabot in #933
  • Bump terser from 5.13.1 to 5.14.2 in /src/AzureIoTHub.Portal/Client/assets by @dependabot in #944
  • Bump docker/build-push-action from 3.0.0 to 3.1.0 by @dependabot in #952
  • Bump Swashbuckle.AspNetCore from 6.3.2 to 6.4.0 in /src by @dependabot in #951
  • Bump Microsoft.ApplicationInsights.AspNetCore from 2.20.0 to 2.21.0 in /src by @dependabot in #954
  • Bump Microsoft.Graph from 4.34.0 to 4.35.0 in /src by @dependabot in #955

Full Changelog: v2.4.0...v2.5.0

v2.4.0

01 Jul 12:53
e6f25f0
Compare
Choose a tag to compare

What's Changed

Breaking changes

N/A

New features

Bug fixings

Minor changes

v2.3.4

29 Jun 14:49
Compare
Choose a tag to compare

What's new?

New options are now present on the portal

  • OIDC__ValidateIssuer

    Validation of the issuer mitigates forwarding attacks that can occur when an IdentityProvider represents multiple tenants and signs tokens with the same keys. It is possible that a token issued for the same audience could be from a different tenant. For example an application could accept users from contoso.onmicrosoft.com but not fabrikam.onmicrosoft.com, both valid tenants. An application that accepts tokens from fabrikam could forward them to the application that accepts tokens for contoso. This boolean only applies to default issuer validation. If IssuerValidator is set, it will be called regardless of whether this property is true or false. The default is true.

  • OIDC__ValidateAudience

    Validation of the audience, mitigates forwarding attacks. For example, a site that receives a token, could not replay it to another side. A forwarded token would contain the audience of the original site. This boolean only applies to default audience validation. If AudienceValidator is set, it will be called regardless of whether this property is true or false. The default is true.

  • OIDC__ValidateLifetime

    This boolean only applies to default lifetime validation. If LifetimeValidator is set, it will be called regardless of whether this property is true or false. The default is true.

  • OIDC__ValidateIssuerSigningKey

    It is possible for tokens to contain the public key needed to check the signature. For example, X509Data can be hydrated into an X509Certificate, which can be used to validate the signature. In these cases it is important to validate the SigningKey that was used to validate the signature. This boolean only applies to default signing key validation. If IssuerSigningKeyValidator is set, it will be called regardless of whether this property is true or false. The default is false.

  • OIDC_ValidateActor

    If an actor token is detected, whether it should be validated. The default is false.

  • OIDC_ValidateTokenReplay

    This boolean only applies to default token replay validation. If TokenReplayValidator is set, it will be called regardless of whether this property is true or false. The default is false.

  • UseSecurityHeaders

    This boolean adds the following headers to all responses :
    X-Content-Type-Options: nosniff
    Strict-Transport-Security: max-age=31536000; includeSubDomains - only applied to HTTPS responses
    X-Frame-Options: Deny - only applied to text/html responses
    X-XSS-Protection: 1; mode=block - only applied to text/html responses
    Referrer-Policy: strict-origin-when-cross-origin - only applied to text/html responses
    Content-Security-Policy: object-src 'none'; form-action 'self'; frame-ancestors 'none' - only applied to text/html responses

Fix CSP restrictions

Add OIDC MetadataUrl to authorized frame ancestors.

Full Changelog: v2.3.0...v2.3.4

v2.3.3

29 Jun 06:50
Compare
Choose a tag to compare
v2.3.3 Pre-release
Pre-release

Full Changelog: v2.3.2...v2.3.3

v2.3.2

28 Jun 09:32
Compare
Choose a tag to compare
v2.3.2 Pre-release
Pre-release

What's Changed

Security constraints updates

CSP: Frame Ancessor changes

We added the OIDC endpoint to the authorized frame ancestors for the portal.
This is related to the issue #878

See CSP: frame-ancestors for more information about this setting

v2.3.1

28 Jun 08:56
Compare
Choose a tag to compare
v2.3.1 Pre-release
Pre-release

What's Changed

Configuration changes

With this version you can now disable some OIDC token validations.
New options are now present on the portal:

  • OIDC__ValidateIssuer

    Validation of the issuer mitigates forwarding attacks that can occur when an IdentityProvider represents multiple tenants and signs tokens with the same keys. It is possible that a token issued for the same audience could be from a different tenant. For example an application could accept users from contoso.onmicrosoft.com but not fabrikam.onmicrosoft.com, both valid tenants. An application that accepts tokens from fabrikam could forward them to the application that accepts tokens for contoso. This boolean only applies to default issuer validation. If IssuerValidator is set, it will be called regardless of whether this property is true or false. The default is true.

  • OIDC__ValidateAudience

    Validation of the audience, mitigates forwarding attacks. For example, a site that receives a token, could not replay it to another side. A forwarded token would contain the audience of the original site. This boolean only applies to default audience validation. If AudienceValidator is set, it will be called regardless of whether this property is true or false. The default is true.

  • OIDC__ValidateLifetime

    This boolean only applies to default lifetime validation. If LifetimeValidator is set, it will be called regardless of whether this property is true or false. The default is true.

  • OIDC__ValidateIssuerSigningKey

    It is possible for tokens to contain the public key needed to check the signature. For example, X509Data can be hydrated into an X509Certificate, which can be used to validate the signature. In these cases it is important to validate the SigningKey that was used to validate the signature. This boolean only applies to default signing key validation. If IssuerSigningKeyValidator is set, it will be called regardless of whether this property is true or false. The default is false.