[JIRA] Commented: (SSPCPP-507) Insert record failed Violation of PRIMARY KEY constraint with ODBC plugin

[Scott Cantor (JIRA)]

    [ https://issues.shibboleth.net/jira/browse/SSPCPP-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14443#comment-14443 ] 

Scott Cantor commented on SSPCPP-507:
-------------------------------------

That's great information, thanks. When you say "logout from the IdP isn't happening", can you explain how you're trying to do logout here and what all is involved? Since we don't support logout in our IdP, I need to know if you're using a non-Shibboleth IdP or what all you're doing. My assumption from the issue in 508 is that you really are seeing an issue with the IdP, and that in fact it's sending the original user's data back to the SP, rather than an issue with the SP itself. Feel free to comment over in that bug.

Meanwhile, yes, you're exactly right about the reverse index issue. Are you hitting it with test users here with a fixed NameID? Does the bug show up outside that scenario?

You're correct that it's designed to allow for test users, but also just in general to turn off a major source of overhead that's only needed if SAML logout is being used (very rare for most).

I'll follow up more once I have time to dig into the behavior of this code specifically.

> Insert record failed Violation of PRIMARY KEY constraint with ODBC plugin
> -------------------------------------------------------------------------
>
>                 Key: SSPCPP-507
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-507
>             Project: Shibboleth SP - C++
>          Issue Type: Bug
>      Security Level: Standard(Standard bug, may impact functionality but does not represent a security vulnerability ) 
>          Components: Session Cache
>    Affects Versions: 2.5.0
>         Environment: Windows 2008 R2 on Azure.
>            Reporter: pbrears at idp.protectnetwork.org
>            Assignee: Scott Cantor
>              Labels: Session
>         Attachments: shiblogs.zip
>
>
> Using two servers with the odbc connection plugin for the storage service you can occasionally get 'insert record failed' 'Violation of PRIMARY KEY constraint' logged
> We're using "SQL Server Native Client 10.0" driver to access SQL azure for the db
> There are two servers in the non sticky load balancer. It's likely that /SAML/POST and /Secure are landing on different boxes.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira