inconsistency with sp_private_key and sp_certificate values about esaml

[arekinath]

I know it might be a lot of trouble, and perhaps comes too late for you, but this should be fixed on the new API in the "develop" branch. There's a lot more documentation and examples in there, too.

Rather than having multiple places that deal with this now, there's just the esaml_sp record, and if you leave it without a key and certificate they will default to undefined and everything should deal with that.

I've tested with the examples/sp code, just commenting out the key = .. and certificate = .. lines and it seems to generate unsigned metadata and authnrequests fine.