InCommon uses MDA in production
Description
Environment
depends on
Activity
Ian YoungAugust 5, 2024 at 3:07 PM
Resolved by 1.0.0, again pretty much by definition.
Ian YoungNovember 29, 2015 at 4:49 PMEdited
The current InCommon draft import tooling uses the following stages that are not part of the current 0.9.0 snapshot, and would ideally be imported from elsewhere (mostly the ukf-mda
project):
NamespacesStrippingStage
(https://shibboleth.atlassian.net/browse/MDA-150#icft=MDA-150)UKItemIdentificationStrategy
(probably in a more generic form without the special cases for UK-format ID values) (https://shibboleth.atlassian.net/browse/MDA-156#icft=MDA-156)EntityAttributeFilteringStage
(https://shibboleth.atlassian.net/browse/MDA-55#icft=MDA-55)ElementWhitespaceTrimmingStage
(https://shibboleth.atlassian.net/browse/MDA-109#icft=MDA-109)X509ValidationStage
and some of the individual validation rules:X509RSAKeyLengthValidator
(https://shibboleth.atlassian.net/browse/MDA-74#icft=MDA-74),X509RSAExponentValidator
(https://shibboleth.atlassian.net/browse/MDA-155#icft=MDA-155),X509RSAOpenSSLBlacklistValidator
(https://shibboleth.atlassian.net/browse/MDA-69#icft=MDA-69)
We should try and get the above into 0.9.0 if possible.
In addition, some Xalan extension functions (date manipulation and, less importantly, Base64 text wrapping) from the sdss-xalan-md
project are also used, and it would be useful to have them incorporated as stages so that we can move away from the use of Xalan in production in the longer term (perhaps in 0.10.0).
Ian YoungNovember 9, 2015 at 12:41 PM
Assigning to 1.0.0, pretty much by definition.
Scott CantorNovember 2, 2015 at 7:09 PM
My suggestion would be that you speak to Shel and/or SteveZ about this. JISC asked a question on the last Board call about the need to get a 0.9 release done, and I deferred to Ian somewhat and they were I thnk going to go off and speak to him about it.
If this needs to be an actual deliverable of the project, we would need more time from its author or identify an alternate resource. Nobody else on the project would be prepared to take it on. This is the same answer I'm giving for any large technical debt we're asked to take on. Need a body, or isn't going to happen.
This isn't an "issue" in the traditional sense of the word. This is a heads up that InCommon has been using MDA in a beta environment for well over a year. On January 11, 2016, we will begin importing eduGAIN in production. At that point, MDA becomes critical infrastructure for InCommon. Well, actually, MDA already is critical infrastructure since we are fully committed to our path forward.
I see that MDA is "In Development." I'm not sure what that means but please accept our request to elevate MDA to "production quality software," whatever that means.