Attribute/IdPAttribute

Rod Widdowson rdw at steadingsoftware.com
Wed Sep 25 10:39:56 EDT 2013


[new thread for clarity]

> I think that changes to the IdPv3 APIs, even as unreleased, should get
> a new email thread or JIRA issue and time for me to think about it.

My bad.  I thought about doing that and made the wrong call..

FYI: once I've done the research I'll be creating a thread shortly to
highlight the discussions about moving attribute mapper into
idp-attribute-api and idp-saml-*, which also sort of slid in under the radar
in the "Reverse attribute mapping" discussion.

> I object to the proposed refactoring 
[Snip]

I agree that we should take the refactoring to the dev meeting.  I'll not be
able to make that meeting so my usual rules apply: If I keep silent on a
topic during discussion I don't get to object to the decision - I'll live
with whatever the meeting tells me to do.  For the record my opinion is that
the rename will really help the maintainability of the attribute code.  It
also feels like something to do sooner that than latter so I’d urge that we
try to get to consensus at that meeting.

I should also say for the record, that the idea is to not only rename
Attribute to IdPAttribute, but also rename ReqestedAttribute to
IdPReqestedAttribute...

> the 24-hour veto.

I 'll emphasize (since I didn't make it clear), but I wasn't putting a limit
on the time for the *discussion* about these topics, it was just a way of
doing the moral equivalent of a "checkout" on old fashioned SCS (but not git
:-).   I let people know of a wide ranging change I want to make to let them
clear things up before I make the change or say "now is a really bad time
for you to do this work, can you hold off for a bit?".  I suspect this is
overkill since in most cases the merge will be pretty trivial.



More information about the dev mailing list