# SAML error after upgrade

**URL:** <https://meta.discourse.org/t/saml-error-after-upgrade/151589>\
**Category:** Support\
**Created:** [May 15, 2020, 10:00am UTC](https://meta.discourse.org/t/saml-error-after-upgrade/151589 "2020-05-15T10:00:35Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)\
**Post date:** [May 15, 2020, 10:00am UTC](https://meta.discourse.org/t/saml-error-after-upgrade/151589/1 "2020-05-15T10:00:36Z")

</div>

Continuing the discussion from [PostgreSQL 12 update](https://meta.discourse.org/t/postgresql-12-update/151236):

After the upgrade, I receive a SAML error on the site, that was not appearing before:

`Sorry, there was an error authorizing your account. Please try again.`

The error log says:

`(saml) Authentication failure! invalid_ticket: OneLogin::RubySaml::ValidationError, http://www.example.com is not a valid audience for this Response - Valid audiences: https://love.public.cat`

I’m using Keycloak SAML client for the site. Was there some change in the plugin that requires additional settings in the plugin? – BTW this plugin uses environment variables that makes it difficult to use it in a multi-site environment.

I tried adding an audience field in Keycloak but this did not change anything. Any idea?

---

_[View the full topic](https://meta.discourse.org/t/saml-error-after-upgrade/151589)._