Version 1.2.6

• Track selector moved to the center of Control Client with auto select and track remember.
• Control Client updated with party type selection and advanced options selector.
• Add change password button in My profile in Control Client.
• Load Control Client dynamic and add a version to recurses URLs.
• OpenID Connect up-party, update secret in separate Control API.
• Fine grained Control API roles and scopes access rights.
• Spelling correction in Control API, change JwtWithCertificateInfo to JwkWithCertificateInfo.
• OpenID Connect down-party and up-party has support for prompt none, login and select_account.
• SAML 2.0 down-party ForceAuthn cannot change identity in a session exists.

Version 1.2.5

• Do not require the jti (JWT ID) claim to present in a client credentials assertion.
• OpenID Connect up-party supports reading up to 50 keys from external OpenID Connect Discovery. If there are more than 10 keys, the X509 certificate information is ignored and the keys are therefore not validated based on a possible certificate.

Version 1.2.4

• Change OpenID Connect Discovery element subject_types_supported to say public.
• Add support for organization in SAML 2.0 metadata.
• SAML 2.0 to JWT claim mapping changed to make it possible to change the default mappings to JWT for claim types:
  • email
  • given_name
  • family_name
  • role

Version 1.2.3

• Updated to .NET 8.
• Add page specific CSS tags at the page-container level, making it possible to differentiate between the pages.
• Limit to maximum 2,000 up-parties and 2,000 down-parties per track.

If you are upgrading an existing FoxIDs installation please change the .NET version to .NET 8 on all four App Services slots after successfully upgrading to this version. However, this version runs fine on both .NET 7 and .NET 8.
The .NET version is set to .NET 8 under the App Service General settings.

Version 1.2.2

• Add support for 24 additional languages.
• FoxIDs support the following languages:
  • Bulgarian (bg)
  • Catalan (ca)
  • Croatian (hr)
  • Czech (cs)
  • Danish (da)
  • Dutch (nl)
  • English (en)
  • Estonian (et)
  • Finnish (fi)
  • French (fr)
  • German (de)
  • Greek (el)
  • Icelandic (is)
  • Italian (it)
  • Latvian (lv)
  • Lithuanian (lt)
  • Norwegian (nb)
  • Polish (pl)
  • Portuguese (pt)
  • Romanian (ro)
  • Slovak (sk)
  • Slovenian (sl)
  • Spanish (es)
  • Swedish (sv)
  • Turkish (tr)
  • Ukrainian (uk)

Version 1.2.1

• Error in SAML 2.0 nullable type conversion resolved. The error made it impossible to read property AssertionConsumerServiceIndex and AttributeConsumingServiceIndex in a SAML 2.0 Authn Request because the type is nullable int.
• Log default cached warnings, errors, and critical errors in the Plan's application insights.

Version 1.2.0

• Support larger claim process values but at the same time limiting the total combined max length.
• Improve OIDC user info endpoint error message.
• Control Client validate tokens with OIDC user info endpoint.
• Read SAML 2.0 bindings from HTTP method on received SAML 2.0 request and SAML 2.0 response.
• User .NET token max size TokenValidationParameters.DefaultMaximumTokenSizeInBytes (256.000 bytes) for JWT and SAML 2.0.
• Accept to process single claim values and in total up to 200,000 characters.
• Internal created claim up to 10,000 characters.
• Internal created named claims and formats up to 1,000 characters.
• Underlying ITfoxtec components contain symbols packages.

Version 1.1.5

• SAML 2.0 up-party redirect binding only validate the certificate that can verify the signature. This has previously been changed for post bindings.
• Accept to process claim values up to 10,000 characters.
• Internal created claim and formats up to 4,000 characters.

Bugs resolved:

• Click email text element on login page return bug.

Version 1.1.4

• Use general constants in grants and sequences.

Bugs resolved:

• Incorrect id length in grants.

Version 1.1.3

• Increase IDs maximum lengths in relation to tenant, track and party names lengths.
• Control API return usage log count with one decimal.

Bugs resolved:

• Incorrect formatted log property bug.