InCommon metadata support

[Andrew Morgan <>]

On Tue, 20 Mar 2018, Andrew Morgan wrote:

> I received an InCommon Baseline: Metadata Health Check report yesterday, so 
> I've been working on becoming compliant for my IDP and 1 SP.

...

> https://spaces.internet2.edu/display/BE/Implementing+Baseline+Expectations+in+InCommon+Metadata
>
> Logo URL subject to the following test conditions:
>
> REQUIRED:
> - Results in a ‘200’ based on an HTTP GET
>
> RECOMMENDED:
> - Returns a base64-encoded PNG with the MIME type image/png
> - Is 80 pixels in width by 60 pixels in height
> - Has a transparent background

I have a follow-up question now that the conflicting information has been 
resolved.

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?

Thanks,
        Andy