!!! Overview
[{$pagename}] defines mechanisms to support a user porting from one [OpenID Connect Provider] to another, such that [Relying parties|Relying Party] can automatically recognize and verify the change.


[{$pagename}] is a [Specification] from the [OpenID Foundation] [Working Group] [Mobile Operator Discovery, Registration & Authentication]

[{$pagename}] extends [OpenID Connect] to enable an [Relying Party] to recognize when a user logging in via a New [OpenID Connect Provider] is the same user who has previously logged in via an Old [OpenID Connect Provider]. That is, it enables porting between [OpenID Connect Providers] to be handled automatically by Relying parties|Relying Party]. The central idea is that the user logs into both Old and New OPs in a single session to establish the link between the user's accounts at each. Subsequently, [Relying parties|Relying Party] can interact with both [OpenID Connect Providers] to confirm that link, without needing the user to repeat the dual logins.

[OpenID Connect] account porting is motivated by (but not limited to) the [GSMA] [Mobile Connect] where [Mobile Network Operators] collectively offer [Federated Identity] services. 

As most jurisdictions allow users to port their mobile phone number between [Mobile Network Operators], and a reasonable expectation of those users will be that their [Mobile Connect] account (provided by those same operators) can also be ported at the same time. There is a significant difference between phone number and account porting, however. Other parties are generally unaware when number porting occurs; they simply keep using the same phone number to communicate with the user. In contrast, [Relying parties|Relying Party] are aware when an [OpenID Connect] account is ported as they interact with a New [OpenID Connect Provider].

!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]