Assuming then that we use a standard convention for the URL endpoints for the various profiles, that leave's the following to be configured:
* Entity ID * Public/Private Keys (only the public to be published) Am I missing any? These look like simple configuration via property/JNDI/whatever with the possible exception that we might want a tool to make it easier to generate and configure appropriate public/private keys. Thoughts? On Mon, Jun 29, 2009 at 1:26 PM, Marvin Addison <marvin.addi...@gmail.com>wrote: > > One of the optional components of the IdP meta data is Organizational > > information. Does anyone feel like they would actually publish that? > > We don't publish any of that for our Shib/InCommon participation, and > wouldn't likely for CAS either. From my experience, metadata > administration is a pain, so anything that can be done to facilitate > it would be helpful. That said, requiring more work for optional > fields sounds fair. > > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
