Remove Legacy (V2) scripting support for attribute resolver.
Completed
Description fields
Basics
Logistics
Basics
Logistics
Description
In V3 we introduced two legacy classes to help people move over to V3
edu.internet2.middleware.shibboleth.common.attribute.provider.V2SAMLProfileRequestContext which was injected as profileRequestContext
{{edu.internet2.middleware.shibboleth.common.attribute.provider.BasicAttribute}} which was available to allow people to create result attributes.
The former is fully replacable by use of the V3 native profile context, the latter has no use outside rhino (and possibly not even there post java 7) since the attribute is created for you.
Hence in V3.4.4 both issue deprecation warning.
The use of edu... is smelly and does cause some packaging problems. But most of all I don't believe any of it can be justified in V4.
So we should remove them. I'll take the case to do the work but not start on it for a couple of Months (June-July) to allow others to demur.
In V3 we introduced two legacy classes to help people move over to V3
edu.internet2.middleware.shibboleth.common.attribute.provider.V2SAMLProfileRequestContextwhich was injected asprofileRequestContext{{edu.internet2.middleware.shibboleth.common.attribute.provider.BasicAttribute}} which was available to allow people to create result attributes.
The former is fully replacable by use of the V3 native profile context, the latter has no use outside rhino (and possibly not even there post java 7) since the attribute is created for you.
Hence in V3.4.4 both issue deprecation warning.
The use of
edu...is smelly and does cause some packaging problems. But most of all I don't believe any of it can be justified in V4.So we should remove them. I'll take the case to do the work but not start on it for a couple of Months (June-July) to allow others to demur.