InCommon metadata support

["Wessel, Keith" <>]

I suspect those logos are coming from entities from other federations added 
to the aggregate courtesy of Edugain.

As for if InCommon plans to support embedded logos in the future, I'll let 
someone from InCommon staff answer that.

Keith


-----Original Message-----
From: 

 
<>
 On Behalf Of Daniel Crisman
Sent: Tuesday, March 27, 2018 9:36 AM
To: 

Subject: Re: [Metadata-Support] Re: conflicting metadata requirements from 
InCommon

Huh, well 500 of the 3519 Logos I see in the aggregate are embedded.  I 
rather like the option to not have to download the logo every time one of my 
users logs in.

Anyone know if that was a willful choice to remove the upload option or did 
it just get forgotten during some code update?  Was there some other process 
to get metadata to the federation in the past that had an embedded image 
option?

dc 
________________________________________
From: 

 
<>
 on behalf of Wessel, Keith 
<>
Sent: Tuesday, March 27, 2018 10:00
To: 

Subject: RE: [Metadata-Support] Re: conflicting metadata requirements from 
InCommon

Last I checked, the Federation Manager doesn't support uploading of images to 
be embedded. The only space for an image in the federation manager's IdP and 
SP pages is a URL.

Keith


-----Original Message-----
From: 

 
<>
 On Behalf Of Daniel Crisman
Sent: Tuesday, March 27, 2018 8:55 AM
To: 

Subject: Re: [Metadata-Support] Re: conflicting metadata requirements from 
InCommon

The base64 image data for when the image is being embedded in the xml 
directly rather than being served from a URL.

On that note, anyone know why the Baseline Expectations require "a valid 
HTTPS Logo URL" as the only option, not allowing the embedded in Metadata 
option?

dc