# SAML configuration issue

**URL:** <https://community.sonarsource.com/t/saml-configuration-issue/143273>\
**Category:** SonarQube Server / Community Build\
**Tags:** saml, sonarqube\
**Created:** [June 23, 2025, 11:43am UTC](https://community.sonarsource.com/t/saml-configuration-issue/143273 "2025-06-23T11:43:19Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [June 24, 2025, 8:15am UTC](https://community.sonarsource.com/t/saml-configuration-issue/143273/4 "2025-06-24T08:15:21Z")

</div>

Hey there.

It looks like the real issue is here:

`java.lang.IllegalArgumentException: Illegal base64 character d`

Take a look at this post:

> [@Okta SSO breaks after 2025.1 upgrade](https://community.sonarsource.com/t/okta-sso-breaks-after-2025-1-upgrade/138613/2):
>
> Fixed! 1.Go to Administration\>Configuration\>Authentication\>SAML 2.Make sure to copy your settings 3.Disable configuration 4.Delete it 5.Create a new one 6.Paste the saved settings 7.Should be working normally. Basically the update has messed with the configuration on the database side somehow, if you delete your SAML configuration and create a new one with the same parameters should make it work again!

---

_[View the full topic](https://community.sonarsource.com/t/saml-configuration-issue/143273)._