Body: <p>I'm running Craft CMS Pro v3.9.1.</p>
  <p>We're trying to interface a Craft site with a partner site. The idea being that the user logs into our site with their Craft credentials then, if needed, click a link on the page to the partner site and be logged in via SSO with their Craft creds.</p>
  <p>We've installed the SAML Identity Provider plugin in Craft and added Craft as the identity provider. We traded metadata with our partner and have them added as a service provider in Craft. As far as we know, they've correctly added us on their side.</p>
  <p>So, we login to our Craft site, click the link to connect to the partner site and get a page of error messages.
  The main error at the top is:</p>
  <p>Argument 2 passed to flipbox\saml\idp\services\messages\Response::create() must be an instance of flipbox\saml\idp\records\ProviderRecord, null given, called in /home/site/wwwroot/vendor/flipboxfactory/saml-idp/src/controllers/LoginController.php on line 79</p>
  <p>Sorry, I'll figure out how to add the entire error page shortly.</p>
  <p>EDIT: Full error:  <a href="https://pastebin.mozilla.org/0NPRtQ2z" rel="nofollow noreferrer">https://pastebin.mozilla.org/0NPRtQ2z</a></p>
  <p>I can't decipher from that whether that's an issue on our side or the partner side.  Or, maybe it's that what we're trying to do just isn't meant to work.</p>
  <p>Any suggestions would be appreciated.
  Thanks,
  Robin</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-12-14T18:36:13.287Z
Comments.Text: same problem here.
Comments.UserDisplayName: Cat Named Dog
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-12-15T19:25:16.053Z
Comments.Text: @good_afternoon
  For us, it turned out to be an error in the Default Entity ID of the plug-in settings.  Instead of https://site.com/ it was entered as https://site.com/web.  Once 'web' was removed, and the metadata regenerated/uploaded, everything started working fine.
  Hope that helps. - Robin
Comments.UserDisplayName: RobinH
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-12-16T16:35:40.403Z
Comments.Text: For some reason the default entity id "my-site.ddev.site" messed it up. I removed the url format and made the id something like "my-site" and it "fixed" it. weird. thanks for your help! can't say i'd feel comfortable spending $200 on this plugin and using it on a production website though. littered with 500 errors and no documentation.
Comments.UserDisplayName: Cat Named Dog
Tags: <plugins>
Title: Craft as IdP using Saml Identity Provider Plugin
ThreadText: # Craft as IdP using Saml Identity Provider Plugin
  
  (Asked by: username_0 on 2023-09-12)
  
  I'm running Craft CMS Pro v3.9.1.
  
  We're trying to interface a Craft site with a partner site. The idea being that the user logs into our site with their Craft credentials then, if needed, click a link on the page to the partner site and be logged in via SSO with their Craft creds.
  
  We've installed the SAML Identity Provider plugin in Craft and added Craft as the identity provider. We traded metadata with our partner and have them added as a service provider in Craft. As far as we know, they've correctly added us on their side.
  
  So, we login to our Craft site, click the link to connect to the partner site and get a page of error messages.
  The main error at the top is:
  
  Argument 2 passed to flipbox\saml\idp\services\messages\Response::create() must be an instance of flipbox\saml\idp\records\ProviderRecord, null given, called in /home/site/wwwroot/vendor/flipboxfactory/saml-idp/src/controllers/LoginController.php on line 79
  
  Sorry, I'll figure out how to add the entire error page shortly.
  
  EDIT: Full error: <https://pastebin.mozilla.org/0NPRtQ2z>
  
  I can't decipher from that whether that's an issue on our side or the partner side. Or, maybe it's that what we're trying to do just isn't meant to work.
  
  Any suggestions would be appreciated.
  Thanks,
  Robin
  
  **Tags:** plugins
  
  > **Comments:**
  > **username_1**: same problem here.  
  > **username_0**: @good_afternoon For us, it turned out to be an error in the Default Entity ID of the plug-in settings.  Instead of https://site.com/ it was entered as https://site.com/web.  Once 'web' was removed, and the metadata regenerated/uploaded, everything started working fine. Hope that helps. - Robin  
  > **username_1**: For some reason the default entity id "my-site.ddev.site" messed it up. I removed the url format and made the id something like "my-site" and it "fixed" it. weird. thanks for your help! can't say i'd feel comfortable spending $200 on this plugin and using it on a production website though. littered with 500 errors and no documentation.  
  
  ---
  
  ## 0 answers
  
  