InCommon metadata support

["Wessel, Keith" <>]

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
________________________________________
From: 

 
<>
 on behalf of Andrew Morgan 
<>
Sent: Thursday, March 22, 2018 18:28
To: 

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

Thanks for the clarification and documentation update!

        Andy


On Thu, 22 Mar 2018, Nick Roy wrote:

> Yes, Chris is correct. I will fix the documentation so it does not
> require base64 encoding for URLs.
>
> Nick
>
> On 3/22/18 2:56 PM, Christopher Bongaarts wrote:
>> On 3/22/2018 3:45 PM, Andrew Morgan wrote:
>>> I have our logo in 80x60 PNG format.  I have created a base64-encoded
>>> version of it.  When I place the base64-encoded file on my IDP's web
>>> server, my browser is unable to display the image.  Here are 3
>>> different versions of the image:
>>>
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__login.oregonstate.edu_images_osu-2Dsmall.png&d=DwIDAw&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=-tCl5ucpxA3yY0RDdWparA&m=SnYomWAGyh11I0Mn9fqVCsJYR2U4eSg8zxoKhYYXmrU&s=wDbN82_6rKqiSpd9wUNza9AO1OsDEBAUGNKnS83S6nc&e=
>>>  - the original image file
>>>  - file reports "PNG image data, 80 x 60, 8-bit/color RGBA,
>>> non-interlaced"
>>>
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__login.oregonstate.edu_images_osu-2Dsmall-2Db64.png&d=DwIDAw&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=-tCl5ucpxA3yY0RDdWparA&m=SnYomWAGyh11I0Mn9fqVCsJYR2U4eSg8zxoKhYYXmrU&s=rNYNcq6S900USJZQlZW1W_tlubAYyiCdtU0IOBAon3o&e=
>>>  - base64 encoded
>>>  - file reports "ASCII text, with very long lines"
>>>
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__login.oregonstate.edu_images_osu-2Dsmall-2Db64-2Dinline.png&d=DwIDAw&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=-tCl5ucpxA3yY0RDdWparA&m=SnYomWAGyh11I0Mn9fqVCsJYR2U4eSg8zxoKhYYXmrU&s=QXPXvn-pBURbVZi1DE4ITiDuhoJG8jczqcDD8okhDVc&e=
>>>  - base64 encoded and prefixed with "data:image/png;base64,"
>>>  - file reports "ASCII text, with very long lines"
>>>
>>>
>>> What is the right way to meet the base64-encoded recommendation?  Does
>>> base64 encoding only apply when using an inline Data URI element?
>>
>> The first one, and yes.
>>
>> --
>> %%  Christopher A. Bongaarts   %%  
>> 
>>           %%
>> %%  OIT - Identity Management  %%  
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__umn.edu_-7Ecab&d=DwIDAw&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=-tCl5ucpxA3yY0RDdWparA&m=SnYomWAGyh11I0Mn9fqVCsJYR2U4eSg8zxoKhYYXmrU&s=Xabkk4ig0cwHZxOUyCvRkONwoau0Y8PviRo_7CNxQks&e=
>>   %%
>> %%  University of Minnesota    %%  +1 (612) 625-1809    %%
>>