Unable to locate a SAML 2.0 ACS endpoint to use for response

[Mr. Christopher Bland]

Hi All,

For anyone who has my same issue after configuring the Native SP ODBC Storage Service, I resolved my issue by taking Scott’s advice.  I went back to my default working config with the following changes

1) Added ODBC Storage

    <!-- The OutOfProcess section contains properties affecting the shibd daemon. -->
    <OutOfProcess logger="shibd.logger">
        <Extensions>
            <Library path="odbc-store.so" fatal="true"/>
        </Extensions>
    </OutOfProcess>

    <!-- This set of components stores sessions and other persistent data in an ODBC database. -->
    <StorageService type="ODBC" id="db" cleanupInterval="900">
        <ConnectionString><![CDATA[
            DRIVER=MySQL;SERVER=db-server;USER=shibd_usr;PASSWORD=password;DATABASE=shibboleth
        ]]>
        </ConnectionString>
    </StorageService>
    <SessionCache type="StorageService" StorageService="db" cacheTimeout="3600" inprocTimeout="900" cleanupInterval="900" />
    <ReplayCache StorageService="db" />
    <ArtifactMap StorageService="db" artifactTTL="180" />

2) Just changed the relayState in the Sessions tag

<Sessions lifetime="28800" timeout="3600" relayState="ss:db”

There may be some extra stuff no longer needed in step one that came from the NativeSPODBCStorageService doc.

-Chris

> On Jun 17, 2017, at 12:15 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> 
> On 6/15/17, 9:49 PM, "users on behalf of Mr. Christopher Bland" <users-bounces at shibboleth.net on behalf of chris at fdu.edu> wrote:
> 
>> My config looks like this
> 
> You've put in all kinds of manual, unnecessary material inside the <Sessions> element in place of the proper way to configure an SP, which is handled now with the simple <SSO> and <Logout> elements that auto-configure a lot of the machinery that used to be done by hand. Having removed those, you've put in some of the manual bits but left out all the AssertionConsumerService elements, for example, which is certainly why it's breaking.
> 
> I don't know what example you're following, but it isn't anything recent. The SP ships with the right examples, and they use the <SSO> element now to auto-establish all the endpoints.
> 
> If you're under the impression you need to do this because of the ODBC thing, you don't, you can override the relayState setting inside the <Sessions> element.
> 
> I can't imagine why you'd need to use ODBC for the relay state though, if you can't do it in memory, I'd just go back to cookies.
> 
> -- Scott
> 
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net