Skip to content

Commit

Permalink
Include OAuth specifics in the interop spec
Browse files Browse the repository at this point in the history
Include OAuth specifics in the interop spec
  • Loading branch information
appsdesh committed Jan 12, 2024
1 parent d4222fd commit 5e59386
Showing 1 changed file with 0 additions and 13 deletions.
13 changes: 0 additions & 13 deletions openid-caep-interoperability-profile-1_0.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,19 +72,6 @@ normative:
ins: A. Tulshibagwale
name: Atul Tulshibagwale
org: SGNL
RFC7525: # Recommendations for Secure Use of Transport Layer Security
RFC6125: # Representation and Verification of Domain-Based Application Service Identity within Internet Public Key
# Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
RFC6750: # The OAuth 2.0 Authorization Framework: Bearer Token Usage
RFC8414: # OAuth 2.0 Authorization Server Metadata
RFC6749:
target: https://www.rfc-editor.org/info/rfc6749
title: The OAuth 2.0 Authorization Framework
author:
-

This comment has been minimized.

Copy link
@tulshi

tulshi Jan 12, 2024

Contributor

You need the RFC lines, you just don't need the details within the RFC

ins: D. Hardt, Ed
name: Dick Hardt
org: Microsoft

--- abstract
This document defines an interoperability profile for implementations of the Shared Signals Framework (SSF) {{SSF}}, the Continuous Access Evaluation Profile (CAEP) {{CAEP}}. This also profiles The OAuth 2.0 Authorization Framework {{RFC6749}} usage in the context of the SSF framework. The interoperability should It is organized around use-cases that improve security of authenticated sessions. It specifies certain optional elements from within the SSF and CAEP specifications as being required to be supported in order to be considered as an interoperable implementation.
Expand Down

0 comments on commit 5e59386

Please sign in to comment.