InCommon metadata support

[Nick Roy <>]

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://login.oregonstate.edu/images/osu-small.png
>>  - the original image file
>>  - file reports "PNG image data, 80 x 60, 8-bit/color RGBA,
>> non-interlaced"
>>
>> https://login.oregonstate.edu/images/osu-small-b64.png
>>  - base64 encoded
>>  - file reports "ASCII text, with very long lines"
>>
>> https://login.oregonstate.edu/images/osu-small-b64-inline.png
>>  - 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  %%  http://umn.edu/~cab  %%
> %%  University of Minnesota    %%  +1 (612) 625-1809    %%
>