Skip to Content.
Sympa Menu

technical-discuss - Re: [InC-Technical] InCommon Baseline Expectations Metadata Requirements

Subject: InCommon Technical Discussions

List archive

Re: [InC-Technical] InCommon Baseline Expectations Metadata Requirements


Chronological Thread 
  • From: David Langenberg <>
  • To: Scott Koranda <>, Nick Roy <>
  • Cc: "Cantor, Scott" <>, "" <>
  • Subject: Re: [InC-Technical] InCommon Baseline Expectations Metadata Requirements
  • Date: Thu, 9 Nov 2017 14:31:55 +0000
  • Accept-language: en-US
  • Authentication-results: spf=none (sender IP is ) ;
  • Ironport-phdr: 9a23:UjSCSRGoxOe71uFFHMXWV51GYnF86YWxBRYc798ds5kLTJ7yociwAkXT6L1XgUPTWs2DsrQf2rqQ6/iocFdDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBXdrXKo8DEdBAj0OxZrKeTpAI7SiNm82/yv95HJbQhFgDmwbaluIBmqsA7cqtQYjYx+J6gr1xDHuGFIe+NYxWNpIVKcgRPx7dqu8ZBg7ipdpesv+9ZPXqvmcas4S6dYDCk9PGAu+MLrrxjDQhCR6XYaT24bjwBHAwnB7BH9Q5fxri73vfdz1SWGIcH7S60/VC+85Kl3VhDnlCYHNyY48G7JjMxwkLlbqw+lqxBm3oLYfJ2ZOP94c6jAf90VWHBBU95RWSJfH428c4UBAekPPelaoYb9pkcBohSlCAmjGO/vzyVFimPs0KA41ekqDAHI3BYnH9ILqHnaos/6NLkTUe+o0aLGyy/Mb/VZ2Tjj7ojHaQ4uoeuDXbltdsfe1FMgFx3bgVWUsoHlIi+a1uQMs2eH9eVgWuWvh3Q5pA5svzii38EhgZTKiIIN0l3I6Dl1zYkvKdC3SkN3e9CpHZpKuy2HOYZ7TdsuT39ptSom17ELvIC3cScOxZkiyBPTd+CLfo2L7x3+W+ucJCp3iG95dL6ighu97FKvxvPhWcSx1FtHoTZKnsTJu30D2BHe6suKR/1g9Um7wzmPzRrc6uRcLEA0i6XbL5khz6YomJcPtkrPAjH6lFzrgqGOa0ko4++o5P/5bbn8oZ+cKpN0hRr5MqQznMywHP40MhAUX2ic5eSzyqHs/VH4QLVNiP06iK7ZsI3GJcQfoa65BAxV3pw/5Ba4CjeqyNUYnX8ZI1JZYB+LkpTlNl7ULP33D/qzmVqhnTZxy/zbMLDsDY3BLn3Zn7fgebZ95VRcyA02zd1H+p1bEK8BL+z3WkLqqdzXEh85Mw2ozOn9B9V90ZkSVnySDa+EKK/Sq0OH5vozI+mQY48YoDf9K/456P7piH85nFgdfa+z0ZsQcnC4Ee1qI1mHbnXwgtcBF2YKsRYkQ+zukVGNTD9TZ22uUKIh/TE7E5mrDYPCRoC2nLyBxzm3EodXZmBAFlCDD23od4OaVPcQdi6eONFunSEZVevpd4h07hqpqBOy6L19J+zY82VMrpHkztFz6+T7mhQ79DgyBMOYhSXFaWB/nSsyQC5+iKZlpl1Vy1Gf3LJ+juACU9Ff+qUafB09MMvwxvJ7B5jWUwTOc9GDRUypCoGqCC88SvosyN8PaE9yHJOvgg2VjHniOKMci7HeXM98yanbxXWkYp8lk3s=
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

I’d say “Transparent background encouraged” If you’re logo is blue and the
IdP’s background color is blue it can cause your logo to disappear or become
unreadable.

Dave

--
David Langenberg
Asst Director, Identity Management
The University of Chicago


On 11/9/17, 7:15 AM,
"
on behalf of Scott Koranda"
<
on behalf of
>
wrote:

Hi,

> And for HTTPS Logo URL:
>
> - Must result in an HTTP 200 in response to a GET request
> - Image must be either a PNG or JPG
> - Image must be 80 pixels in width by 60 in height

I have avoided trying to be specific with my desire for the baseline
requirements for logo since any requirement for logo is new to InCommon.

I am pleasantly surprised to see that you are considering requiring
sensible formats (PNG/JPG) and a required size (80 x 60). Thanks!

As long as you are going this far...

Do you want to add this?

- Image must have a transparent background

Without a transparent background the logos can look "funny" (or
downright obnoxious) when embedded into a discovery service or IdP login
page that has made its own choice for color scheme.

Thanks for your consideration,

Scott K

Attachment: smime.p7s
Description: S/MIME cryptographic signature




Archive powered by MHonArc 2.6.19.

Top of Page