openid / HEART / issues / #5 - Clarify compliance of different components — Bitbucket

Issue #5 closed

Justin Richer created an issue 2016-03-21

Text should be clear that a HEART OAuth AS can also be a HEART OIDC IdP, but that they're not equivalent. We should also be clear that HEART servers and clients can also have additional capabilities but these are not covered by HEART.

Comments (1)

Justin Richer reporter
- changed status to closed
added conformance language for all three specs and their interactions, closes #5

→ <<cset dabd27b48f22>>
- 2016-04-30T17:43:26+00:00
Log in to comment

Assignee: –

Type: bug

Priority: major

Status: closed

Component: –

Votes: 0

Watchers: 1

Jira: the preferred issue tracker for Bitbucket. Join the team!