Shibboleth Developers

["Rod Widdowson" <>]

This is another also "mostly dev only" question... 

Some of the attribute resolvers need a view on the wider world outside 
attributes when they run (e.g.
PrincipalAuthenticationMethodDefinition), or actually add such a view to the 
context passed on to the "user" (Velocity & Scripted).


Obviously the way that the plumbing is done in IdP3 is quite different, but 
is the idea that something like
getAttributeRequestContext() is going to be added to 
net.shibboleth.idp.attribute.resolver.AttributeResolutionContext (or possibly
its parent class?).

If so:
Shall I just leave the definitions that have the need for such a call until 
the plumbing is done?  The Velocity and Scripted
definitions can be added now of course - they will just have a more 
restricted view of the world until the plubing is done.

If not:
How will this plumbing be done?  I'm happy to wait and see, or even be told 
to RTFCode...

On a related matter, just as it is easier to write tests before you write the 
code (or at best shortly after) it is easiest to write
documentation at the same time as the code.  Where the plugins are identical 
of course new documentation is a no-op, but in cases
where APIs have changed it would be nice to capture at least a framework 
document now.  

So what is the plan for V3 documentation?  If things are not ready yet I'm 
happy to just dump stuff in my personal space and move it
over at a later date.

/Rod