# SSO authentication with Centrify **URL:** \ **Category:** Support\ **Created:** [20 Aprile 2017, 4:19am UTC](https://meta.discourse.org/t/sso-authentication-with-centrify/61298 "2017-04-20T04:19:44Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![mjeanson](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@mjeanson](https://meta.discourse.org/u/mjeanson)\ **Post date:** [20 Aprile 2017, 4:19am UTC](https://meta.discourse.org/t/sso-authentication-with-centrify/61298/1 "2017-04-20T04:19:44Z")
Hi, We are trying to use our SSO provider Centrify with Discourse. And we’re having some problems. We installed the SAML plugin ([GitHub - discourse/discourse-saml: Support for SAML in Discourse · GitHub](https://github.com/discourse/discourse-saml)) We have Discourse version v1.8.0.beta9 +25 Below are screenshots of the discourse login setup and some of the logs we currently see. ![](https://global.discourse-cdn.com/meta/original/3X/c/7/c70e3b7b47608d4d9c8e24c9aa7b82e56a1f3a0f.png) The SAML assertion is sending the NameID(user identifier) variable as our active directory samaccountname(email minus domain @f…com). Main thing is that it seems like the SAML assertion goes to the correct place but discourse is not configured properly to process it. Normally, it gives the ‘Bad CSRF’ which I’m not entirely what it means. Assertion URL: http: // discourse\_web\_url/auth/saml/callback Issuer: http: // [cloud.centrify.com/SAML/AppName](http://cloud.centrify.com/SAML/AppName) Audience: http: // discourse\_web\_url Recipient: http: // discourse\_web\_url/auth/saml/callback Identity Provider Info: Sign-In URL: https: // [aac0995.my.centrify.com/applogin/appKey/xxxxx-xxxx-xxxxxx-xxxxxxx/customerId/XXXXXXXX](http://aac0995.my.centrify.com/applogin/appKey/xxxxx-xxxx-xxxxxx-xxxxxxx/customerId/XXXXXXXX) And it has also an associated sign-in certificate Any help would be greatly appreciated!! Thank you, Matthieu --- _[View the full topic](https://meta.discourse.org/t/sso-authentication-with-centrify/61298)._