Error in the idp-process.log

[Cantor, Scott]

Ok, first conclusion: your original question:

I believe the cause of the error in the service config is that you set the name of the bean of the persistent ID JDBC data source to a non-existent bean.

You have:

idp.persistentId.dataSource = shibboleth.PostgreSQLDataSource

That bean is not anywhere in anything you posted, and unfortunately for reasons I won't try and explain (it's due to workarounds for bugs in the original 3.0 release) the Spring config that loads the data source bean into the object that's breaking is doing it in a way that doesn't clearly scream about the bean not existing. You get a less obvious error later when it throws that ConstraintViolation and it's only a code review that really highlights the problem.

That's why I wanted to call timeout and look at this again, I had a suspicion the problem was with the reporting of the cause.

Now, that said:

- I hope your salt property value was sanitized for posting or you just revealed the salt, which means the values you may have generated for people are no longer privacy preserving.

- Before you fix anything in production, you need to test it first because there are still lots of possible problems throughout this configuration that might cause breakage if you were to get the non-deprecated NameID generation to work.

- I still don't understand how you're getting NameIDs out at all, with this service config breaking, but I need to check into that further in the code.

So I'm still looking at it.

-- Scott