New Function in IdP V3.4/V4

[Cantor, Scott]

On 7/19/17, 1:34 PM, "dev on behalf of Rod Widdowson" <dev-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:

> For the record the suggested new functions in these cases are:
>
> 1) Support DBCP from native configuration syntax/deprecate V3P0

That's the sort of thing I tend to not want to do in point releases because it's an invisible change that's pretty substantive. I'm not sure *any* pooling library works when ultimately the drivers all hang you on failed connections half the time, so I'm not sure there's a huge risk, but I'd rather put the risk into the newer version since that's intended to be more thoroughly tested.

New is fine, in other words, but this is a change, rather than something new.

> 2) New “shell refresh” Resource to replace SVN based Resources (and to open the door to git).  Deprecate SVN

Which OTOH is just new. That should get in as soon as we can, and as much as "shell anything" is pretty much a "hack me" sign, it does nothing if somebody doesn't turn it on, so it's fine for upgrades/

> 3) Security custom namespace:
> a. Provide a workable option to the current mainline uses (mostly keys to LDAP).
>  b. Look at configurability of the edge cases, possibly introducing true mixed mode (native spring/custom schema) parsing.
>  c. Deprecate the sec: namespace

Need to know more about that one (even if I created the issue, I don't remember).

> Nonetheless there might be an argument to be made for at least having the design mapped out prior to 3.4 in case it requires
> some configuration underpinnings changed prior to V4.

It's inarguable that it's better to know everything, but having the time to actually do that design far enough to learn anything is much harder.

Anyway, my rule of thumb is that updates to 3.x should be 100% safe and risk free. Any new feature that doesn't risk that is generally ok with me.

-- Scott