Trouble shooting & FAQ

If you get an error when returning from your IdP


You have successfully authenticated on your IdP and are redirected into wire. Wire shows a white page with an error message that contains a lot of machine-readable info.

What we need from you:

  • Your SSO metadata file

  • The SSO login code (eg. wire-3f61d2ce-525c-11ea-b8da-cf641a7b716a; you can find it in the team settings where you registered your IdP)

  • The full browser page with the error message (copy it into your clipboard and insert it into an email to us, or save the page as an html file and send that to us)

With all this information, please get in touch with our customer support.

Do I need any firewall settings?


There is nothing to be done here. There is no internet traffic between your SAML IdP and the wire service. All communication happens via the browser or app.

What should the SAML response look like?

Here is an example that works. Much of this beyond the subject’s NameID is required by the SAML standard. If you can find a more minimal example that still works, we’d be love to take a look.

<saml:Assertion xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" ID="..." IssueInstant="..." Version="2.0">
  <ds:Signature xmlns:ds="">
      <ds:CanonicalizationMethod Algorithm=""/>
      <ds:SignatureMethod Algorithm=""/>
      <ds:Reference URI="#...">
          <ds:Transform Algorithm=""/>
          <ds:Transform Algorithm="">
            <ec:InclusiveNamespaces xmlns:ec="" PrefixList="ds saml"/>
        <ds:DigestMethod Algorithm=""/>
    <saml:NameID Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">...</saml:NameID>
    <saml:SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:bearer">
      <saml:SubjectConfirmationData Address="..." InResponseTo="..." NotOnOrAfter="..."
  <saml:Conditions NotBefore="..." NotOnOrAfter="...">
  <saml:AuthnStatement AuthnInstant="..." SessionNotOnOrAfter="...">
    <saml:SubjectLocality Address="..."/>