[Openid-specs-heart] Health Relationship Trust Profile for OAuth 2.0

[Danny van Leeuwen]

2.1.1.
<http://openid.bitbucket.org/HEART/openid-heart-oauth2.html#rfc.section.2.1.1>
 Full Client with User Delegation
<http://openid.bitbucket.org/HEART/openid-heart-oauth2.html#FullClient>



>From <http://openid.bitbucket.org/HEART/openid-heart-oauth2.html>

The authorization code flow is supported only for confidential clients.
Examples of this client type include web applications and native
applications that can store installation-instance-specific client
credentials securely. Client credentials MUST NOT be shared among instances
[separate or discreet instances?] of a given piece of client software.



>From <http://openid.bitbucket.org/HEART/openid-heart-oauth2.html>

-- 
Danny van Leeuwen
617-304-4681

*Blog www.health-hats.com <http://www.health-hats.com/> discovering the
magic levers of best health*
*Twitter **@healthhats*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20151127/6ce16a7a/attachment.html>