Single SP, multiple applications

Cantor, Scott cantor.2 at osu.edu
Fri Feb 5 10:25:58 EST 2016


> Thanks very much Scott, that makes sense. I felt like I was missing something
> in my model and that explains it. It looks like the best option then will be to
> set up separate entityIDs. I saw that other providers in the InCommon
> federation were doing that but I was hoping I could outsmart the system :).

I wish there was, I don't like that model much.

Using a consistent convention at least tends to allow for release policies based on a regex, which means documentation at least is consistent.

But the main issue is just the extra work for you on all fronts, and that wasn't something the SP caused intentionally, it's just that it was built to solve a different problem.

Some of the extra hassle though would be addressed if InCommon had an API to use to register and maintain the metadata.
 
-- Scott



More information about the users mailing list