Acuo STS 2.0.x Release (June, 2020) - Acuo STS Manager - 3.1 - 3.1 - Ready - Acuo - external - Acuo/Acuo-STS-Manager/3.1/Acuo-STS-Manager-Release-Notes/Acuo-STS-2.0.x-Release-June-2020 - 2024-10-15 - This release includes the following version.

Acuo STS Manager Release Notes

Platform
Acuo
Product
Acuo STS Manager
Release
3.1
License
ft:locale
en-US

This release includes the following version.

  • Acuo STS 2.0.x

Enhancements

  • STS Manager web application is now migrated to the new Hyland UI Framework. Acuo STS 2.0.0 is now compatible with Hyland-UI_1.0.1 .

  • Acuo STS now supports serialization of SubjectRole and PurposeOfUse Claims to a Proper xml format while creating SAML2.0 Assertion.

  • Acuo STS now allows making the ‘AppliesTo’ field optional in WS-Trust RequestSecurityToken object for Token Validation request.

  • Acuo STS now allows you to select your preferred format (NameIdentifierFormat ) for the SAML Assertion “nameId” element by including the “Preferred NameIdentifier format” configuration in STS Manager web application. Acuo STS supports following formats:

    -urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName

    -urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress

    -urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified

    If the selected format cannot be applied to the available “nameId” value, the Acuo STS chooses the “nameId” format as 'urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified'.

  • Acuo STS now supports format validations on claim values based on the selection in the ClaimValueType list. If selected format is “String”, application will accept the claim value without any validation. The following formats are supported- String, Number, NumberWith10Digit, Boolean, URN_OID, URN, OID, URL, URN_OIDandURL, URI, Email, CE, PatientID.

  • Acuo STS now supports adding claim description. Details about a claim can be added through “Description” column in the “Outgoing Claims” page of the STS Manager. The Claim description will be added inside FederationMetadata.xml.

  • Acuo STS now supports removal of Encryption Certificate. You can remove any attached encryption certificate from a Relying Party through the STS Manager web application.

  • Acuo STS now supports the addition of the Authorization Decision Statement. When “AccessConsentPolicy” or “InstanceAccessConsentPolicy” are configured as Outgoing Claim, “AuthzDecisionStatement” section will be added inside SAML2.0 assertion.

  • Acuo STS now supports the addition of the Authentication Statement. The “AuthnStatement” is added in the section inside SAML2.0 assertion. For password authentication, AuthenticationMethod is added as urn:oasis:names:tc:SAML:2.0:ac:classes:Password.

  • Acuo STS now supports the 'holder-of-key' SubjectConfirmationMethod and can successfully generate Encrypted Proof Token.

  • Acuo STS now supports the use of ‘baseAddress’ as token issuer name. If TokenIssuerName, configured inside Acuo.STS.Service.exe.config, is not an URI the application will use the ‘baseAddress’ of the hosted STS as the issuer name.

  • Acuo STS now exports FederationMetadata.xml. The FederationMetadata endpoints are visible inside “Service” page of the STS Manager.

  • Acuo STS now supports the specific requirement of NilRead about fetching User details from active directory without knowing user password. Initial Authentication is done by a common service account. The subject/username can be sent through WS-Trust request claim.