ProfileIdentityProvider is not targeted for survival long-term: it is not needed inside the Identity Service implementation, and it is not needed as part of the Identity Service client API. Hence, its usage by consumers should be replaced by usage of the Identity Service client library.
One subtlety when replacing usage in some consumer is the need to check whether that consumer also interacts with device identity via DeviceIdentityProvider. If so, that issue needs to be handled for that consumer.
See blocking bugs for a non-complete list of consumers that need to be converted.
Comment 1 by blundell@chromium.org
, Feb 7 2018Components: Internals>Services>Identity
Status: Available (was: Untriaged)