AW: crashing IdP db connection

[Cantor, Scott]

> Terrible that IIS isn't case sensitive when using ASP.net Default.aspx
> and default.aspx are both accepted thus confusing the database. Paths
> are case sensitive in IIS, but not ASP.net scripts, so it seems.

The two URLs are different, they just happen to map to the same resource.

Either way, the reason SAML has entityIDs is to avoid this issue, locations are not usable as names. Unfortunately CAS mixes them.

> So your saying, hibernate can be set to accept case insensitive? Is this
> a good idea?

I'm saying that the storage service contract is that keys are case sensitive. Therefore it is required that the database be case sensitive in its matching rules for the context and key columns in the table, and Hibernate must also honor that. How any of that happens is database specific and/or involves Hibernate which I don't know anything about so somebody who does would have to answer that.

In terms of the system's behavior, if it tries to store those records, it shouldn't be getting prevented from doing so.

> Thanks! I will change that. This might be more stable if changed and not
> drop the pool connection to the db, hopefully.... I'll try this first.

I doubt it will affect the behavior, I just thought maybe it wouldn't hang the shutdown and it's just easier than spreading the configuration over two layers of independent software.

-- Scott