Skip to content

77.0.0

Compare
Choose a tag to compare
@cf-identity cf-identity released this 14 Feb 12:32

What's Changed

⚠️ Breaking Changes

  • Remove UAA's ability to act as a SAML identity provider by @hsinn0 in #2638
    • feat: clean up unused DB table service_provider used by UAA-as-SAML-IDP feature by @peterhaochen47 in #2701
  • Remove: deprecated native MFA feature by @peterhaochen47 in #2717
  • Please note that upgrading to this release will clean up all persisted data related to the removed features mentioned above, so please proceed with caution.

Misc

Dependency Bumps

  • Bump Gradle to 8.6 by @strehle in #2707
  • renovate: update dependency nokogiri to v1.16.2 by @strehle in #2713
  • build(deps): bump org.json:json from 20231013 to 20240205 by @dependabot in #2714
  • build(deps): bump org.apache.directory.api:api-ldap-model from 2.1.5 to 2.1.6 by @dependabot in #2715
  • build(deps): bump com.google.zxing:javase from 3.5.2 to 3.5.3 by @dependabot in #2698
  • renovate: update dependency middleman-syntax to v3.4.0 by @strehle in #2706
  • renovate: update dependency nokogiri to v1.16.1 by @strehle in #2709
  • build(deps): bump joda-time:joda-time from 2.12.6 to 2.12.7 by @dependabot in #2710
  • Bump json path from version 2.7.0 to 2.9.0 by @strehle in #2686
  • build(deps): bump actions/dependency-review-action from 3 to 4 by @dependabot in #2685
  • build(deps): bump github.com/onsi/gomega from 1.31.0 to 1.31.1 in /k8s by @dependabot in #2687

Known Issues

  • During the upgrade to this version from UAA v76 or below with canary deployment (where briefly both new and old UAA servers could be running), UAA delete user endpoint might respond with an error even though the user deletion is successful. Mitigation: Delete users after the canary deployment finishes. But if you do run into this issue, you can ignore the error and check whether the user has been successfully deleted after the canary deployment finishes.

Full Changelog: v76.31.0...v77.0.0