Buzz: Questions & Answers

SSO Issues with Buzz

Dennis Killmer

We setup SSO with Buzz a few months ago and it stopped working this week. Did something change on the Agilix side?

The SSO metadata file we use is:

This configuration creates a relying party trust for:

SAML requests from Buzz are being sent with a different identifier.  Here’s an example of a decrypted SAML request:

<samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" ID="_328de988-cfb1-4f02-86ba-682a11465310" Version="2.0"IssueInstant="2015-12-17T17:52:42.6570782Z" IsPassive="false" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"AssertionConsumerServiceURL="">



I have confirmed this by viewing the event viewer on our server:

Comments (3)

Sort by
Brad Marshall
  • Agilix team member

Yes, Dennis. This was an issue that arose on 12/10. The API URL for Buzz was updated to While can still be used independently of Buzz, it would be required to update anywhere you reference the service from to for Buzz integrations (i.e., SSO). 

I am sorry for this frustration.

0 Comment actions Permalink
Dennis Killmer

Hi Brad,

Thank you for letting me know and updating the metafile fixed the issue. I'm sure you are already aware of this, but the following support document sill has the old URL.

Thanks again,


0 Comment actions Permalink
Brad Marshall
  • Agilix team member

Thanks for pointing that out, Dennis. We'll get that URL fixed soon.

0 Comment actions Permalink
Please sign in to leave a comment.