Skip to Content.
Sympa Menu

participants-research - Re: IdP discovery - list 'em all?

Subject: InC Research Participants

List archive

Re: IdP discovery - list 'em all?

Chronological Thread 
  • From: Tom Barton <>
  • To:
  • Subject: Re: IdP discovery - list 'em all?
  • Date: Thu, 1 Sep 2016 14:48:40 -0500
  • Ironport-phdr: 9a23:AM4zQBW4Wv/Ne/SmhGATTBWhxU/V8LGtZVwlr6E/grcLSJyIuqrYZR2Bt8tkgFKBZ4jH8fUM07OQ6P+wHzFbqs/c+Fk5M7VyFDY9wf0MmAIhBMPXQWbaF9XNKxIAIcJZSVV+9Gu6O0UGUOz3ZlnVv2HgpWVKQka3GBR4PNv1G5LfyoGen6D3osWLIlYAuD3oebpoMBS9rB3YsNUNxJFvMas40BDJinpOcONTwGRuY1WJkEXS/MC1qaJk9mx6sug98MgIBbnwdr4kSrpwET8mMms868qtuBXeG1jcrkAAW3kbx0IbSzPO6wv3C9Ko6nP3

I'm interested to understand, if possible, what impedes resolution when the user is given a reasonable error message and an email address to communicate with about it (Jim, you said this has *never* yet been successful, I think - yikes).

Which address(es) is the user provided for contacting their IdP operator? And what message text are they given in hopes that the two will lead to resolution? Are those presented as "press here to send this message to these addresses" or as instruction to send a message to those addresses including the suggested text, or something else?


On 9/1/2016 2:37 PM, Basney, Jim wrote:
On 9/1/16, 12:32 PM, Tom Mitchell wrote:
Yes, I like this. This allows a user to recognize that their institution
needs to do some work to support their research goals, and possibly
causes them to request of their institution that they support these

Taking the other approach, where the identity provider doesn't show up in
discovery, will probably make the user go away or use an unaffiliated
identity provider for access. It does nothing to prompt the identity
provider to support these categories.
Agreed. It helps when the contact email addresses in IdP metadata don't
bounce. I learned today that one of the downsides of having the user send
the email to their IdP operators is they give up when the email bounces...
Good thing we have the user also CC us so we can follow-up.

FWIW, I've reported the bouncing contact email addresses in InCommon
metadata to


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Archive powered by MHonArc 2.6.19.

Top of Page