# SonarQube upgrade to 2025.1.0 impacting SAML Okta authentication

**URL:** <https://community.sonarsource.com/t/sonarqube-upgrade-to-2025-1-0-impacting-saml-okta-authentication/134954>\
**Category:** SonarQube Server / Community Build\
**Created:** [February 11, 2025, 10:41am UTC](https://community.sonarsource.com/t/sonarqube-upgrade-to-2025-1-0-impacting-saml-okta-authentication/134954 "2025-02-11T10:41:37Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![oumayma](https://avatars.discourse-cdn.com/v4/letter/o/e5b9ba/32.png) [@oumayma](https://community.sonarsource.com/u/oumayma)\
**Post date:** [February 12, 2025, 10:52am UTC](https://community.sonarsource.com/t/sonarqube-upgrade-to-2025-1-0-impacting-saml-okta-authentication/134954/3 "2025-02-12T10:52:55Z")

</div>

Hello Colin,

Thank you for your response!  
Exactly, upon checking the logs, I found that the recipient URL diverge:

```auto
Failed to match SubjectConfirmationData@Recipient to any supplied valid recipients: [http://localhost:9000/oauth2/callback/saml]

```

I fixed this issue by overriding the property **Server base URL** under **Administration \> Configuration \> General \> General** in the UI with the current URL of our SonarQube.

If the deployment is done via Helm chart, it can be overridden like below (via the config map):

```auto
sonarqube:
  sonarProperties:
    sonar.core.serverBaseURL: "https://sonar.company.io/"

```

I suggest to add this information to the upgrade release, as it can create a breaking change when upgrading versions, especially when in previous versions we were not used to override this property.  
Oumayma.

---

_[View the full topic](https://community.sonarsource.com/t/sonarqube-upgrade-to-2025-1-0-impacting-saml-okta-authentication/134954)._