[OpenID] RPs accepting https:// identifiers

[Peter Williams]

Doesn't SAML have specific support for the very use case of migrating one id to another? Isn't this the name mapping feature - wherein an SP can record a new SP-Identifier (that can be shared across an affiliation of SPs)? I fear my memory is failing me, on the actual details.

Sounds like we could be borrowing the use case analysis of the OASIS folk, at least - even if the service is ultimately expressed using openid-framework protocols. What matters in standards making is getting common service adopted and put into commodity form.

This might be something the academic SAML folks and openid folks could cooperate on. The academic folk don't seem to be too interested in that particular SAML feature - perhaps lacking a strong, practical use case that the openid view on the world finally opens up, as folks see a need to easily swap out their login openid, across 10 web2.0 sites?



-----Original Message-----
From: general-bounces at openid.net [mailto:general-bounces at openid.net] On Behalf Of SitG Admin
Sent: Monday, August 11, 2008 7:36 PM
To: Martin Atkins
Cc: general at openid.net
Subject: Re: [OpenID] RPs accepting https:// identifiers

>Really this is a specific form of the general problem of how to
>automatically migrate from one identifier to another. Manually updating
>all RPs you've used can be an arduous process, and some RPs don't even
>allow the identifier(s) associated with an account to be changed.

It might be easier to convince them if there were a standard for
letting both URI's (old and new alike) "claim" the other. More like
the reverse of claiming, though, since that's dangerous from either
end; "I am willing to be associated with this URI."

Something that could be automated by Relying Parties.

-Shade
_______________________________________________
general mailing list
general at openid.net
http://openid.net/mailman/listinfo/general