Metadata, examples, best practices?
Jason Gauthier
jgauthier at lastar.com
Wed Nov 27 14:33:25 EST 2013
This is probably an elementary question, and I'm okay wit that... so go easy on me.
I have used shib a few times, and achieved what I wanted to achieve. I am now setting up something a little more elaborate and I want to get things done well from the beginning.
For my environment shib is an SP, and ADFS is the IDP. Just to set the imagery properly.
I have set up a new Apache system with shib SP, and have protected an internal site. I did this just to get the baseline.
Ultimately, this system is going to protect, and reverse proxy several internal sites.
In ADFS I could go the route of one relaying party with multiple assertion consumer endpoints, or I could make one for each "virtualhost".
If I make one (maybe that's bad practice) how do I go about adding additional "md:AssertionConsumerService" records to the metadata?
I attempted to do this, and it came out poorly.
Now, on the subject of metadata (and this might be the most important question)
" <!--
This is example metadata only. Do *NOT* supply it as is without review,
and do *NOT* provide it in real time to your partners.
-->"
What is the preferred method to provide this metadata to ADFS? ( which is my only partner, and it's internal)
I have read through the SP documentation, and I just simply do not see (perhaps because it's not right in my face) the best method to provide metadata.
Is that simply copying what is generated automatically and then modifying it for my needs, and then servicing it up as on another URL, or is there any configuration where serving it up from the "generation handler" valid?
Thanks very much!
More information about the users
mailing list