+xThat's correct. Bu default, it uses a separate cookie.
Don't specify a delegate and the separate cookie will be used.
SAMLController.SSOSessionStore = new DatabaseSSOSessionStore("System.Data.SqlClient", connString, "SAML_SSO_Sessions");
I made the change and get this error in my code:
System.NullReferenceException: Object reference not set to an instance of an object.
at ComponentSpace.SAML2.Bindings.HTTPPostBinding.SendResponse(HttpResponse httpResponse, String targetURL, XmlElement samlMessage, String relayState)
at ComponentSpace.SAML2.InternalSAMLIdentityProvider.InitiateSSO(HttpResponse httpResponse, String userName, SAMLAttribute[] attributes, String authnContext, String relayState, String partnerSP, String assertionConsumerServiceUrl)
at ComponentSpace.SAML2.SAMLIdentityProvider.InitiateSSO(HttpResponse httpResponse, String userName, IDictionary`2 attributes, String relayState, String partnerSP)
However I still don't see any entries in the database and no noticeable SQL errors in the logs. Are the session ID's automatically deleted from the database?
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: The SAML configuration file has been successfully loaded.
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: SAML configuration changes in the directory C:\Websites\RC-Mobile-API are being monitored.
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: The SAML environment has been successfuly initialized.
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: The SAMLConfigurationState is being loaded from the database SSO session store.
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Database provider name: System.Data.SqlClient.
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Database command: SELECT SessionObject FROM SAML_SSO_Sessions WHERE SessionID = @SessionID
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Database parameters:
SessionID=d3e4e15e-328c-44dc-b9de-e673bebef597:SAMLConfigurationState
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: The IdentityProviderSession is being loaded from the database SSO session store.
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Database provider name: System.Data.SqlClient.
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Database command: SELECT SessionObject FROM SAML_SSO_Sessions WHERE SessionID = @SessionID
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Database parameters:
SessionID=d3e4e15e-328c-44dc-b9de-e673bebef597:IdentityProviderSession
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Initiating SSO to the partner service provider
https://www.dotloop.saml.com.ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Identity provider session (d3e4e15e-328c-44dc-b9de-e673bebef597) state:
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: The SAMLConfigurationState is being loaded from the database SSO session store.
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Database provider name: System.Data.SqlClient.
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Database command: SELECT SessionObject FROM SAML_SSO_Sessions WHERE SessionID = @SessionID
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Database parameters:
SessionID=d3e4e15e-328c-44dc-b9de-e673bebef597:SAMLConfigurationState
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: The SAMLConfigurationState is being loaded from the database SSO session store.
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Database provider name: System.Data.SqlClient.
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Database command: SELECT SessionObject FROM SAML_SSO_Sessions WHERE SessionID = @SessionID
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: Database parameters:
SessionID=d3e4e15e-328c-44dc-b9de-e673bebef597:SAMLConfigurationState
ComponentSpace.SAML2 Verbose: 0 : 7688/24: 3/25/2019 4:26:50 PM: XML signature generation was successful.