IdPv3.0.0a1 Miscellaneous Feedback

Nate Klingenstein ndk at internet2.edu
Tue Jul 1 11:47:27 EDT 2014


The entire load test environment should be done except for the LDAP population, which is currently sitting at around 85,000 after running for 41 minutes.  I think I can run a test later today to validate the setup works.

A few comments so far on a1:

1)  Can /conf/authn/ldap-auth-config.xml inherit from idp.properties too?
2)  The decryption key rollover support in idp.properties surprised me.  It's awesome but I don't think many IdP's would use it, so I'd bump those comments to the bottom or omit them entirely.
3)  The packaging and configuration are outstanding and I can't wait to dig in to the rest of it.  I find it all pretty intuitive, though I'm obviously not a representative sample.  I'm deliberately playing "srsly deployer" and ignoring the documentation for now.
4)  I don't think the user explanation of "replay" in messages.properties is going to fly.  The rest of that error is very well written, though, and I don't know what else I'd say.  I guess I'd just yank the part following and including "causing".

Random typos(I will go grammar and spelling police later on):

14, 18, 19-20 could be clearer in metadata-providers.xml
8, attribute-resolver.xml
65, 47 comma splice in messages.properties


I chuckled at this one in messages.properties:

 49 endpoint.title = Unable to Respond
 50 endpoint.message = The login service was unable to identify a compatible way to respond to the requested \
 51                     application. This is generally to due to a misconfiguration on the part of the application \
 52                     and should be reported to the application's support team or owner.



More information about the dev mailing list