Development Test Environment

[Tom Scavo]

On Fri, Mar 20, 2015 at 11:52 AM, Michael Dahlberg <olgamirth at gmail.com> wrote:
>
> On Fri, Mar 20, 2015 at 11:26 AM, Tom Scavo <trscavo at gmail.com> wrote:
>>
>> 1) Assuming you belong to a federation (and assuming the federation
>> accepts test SP metadata), just have them register their SP metadata.
>> (an obvious solution, I know :)
>
> Thanks. We (Bucknell University) belong to the InCommon Federation.  I did
> not know that we could include test SP metadata in the InCommon Federation
> metadata.

There's absolutely no problem registering test SP metadata in InCommon
(which tells me the documentation might be lacking). Test IdP metadata
is a different question altogether:
https://spaces.internet2.edu/x/soHYAg

> As an aside, is the addition of test metadata why some members'
> entityId (for example, PSU) is of the form urn:mace:incommon:psu.edu, while
> ours is of the form https://shib.bucknell.edu/idp/shibboleth ?

No, the use of URNs as entityIDs is a completely different issue. See
the short historical note documented here:
https://spaces.internet2.edu/x/OQVOAg

>> 2) Use REEP https://reep.refeds.org/
>
> If we already belong to InCommon, would it be better to use REEP for test
> metadata?

Actually, no. Every time you copy your metadata, you increase the
chances that something somewhere will go wrong (since it's difficult
to keep the copies in sync).

> I might just use Scott's suggestion and just modify the developers'
> workstations' hosts file.

That's fine too.

Tom