[JIRA] Updated: (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:all-tabpanel ]

Scott Cantor updated SSPCPP-507:
--------------------------------

    Attachment: patched.zip

Patched DLLs for the shibsp libraries and the odbc-store plugin.

To use these, make sure both the IIS half and the shibd half are using these new versions, because some of the other bug fixes have affected the RPC messages in a couple of cases.

We shouldn't need any other updates to the rest of the files, but we'll see how they behave.

> 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
>             Fix For: 2.5.1
>
>         Attachments: patched.zip, shiblogs.zip
>
>          Time Spent: 4 hours
>  Remaining Estimate: 0 minutes
>
> 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