Skip to content

Commit c4f0f85

Browse files
committed
Updates
1. Shayne's suggestion 2. CAEP version
1 parent fd3bcd7 commit c4f0f85

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

openid-caep-interoperability-profile-1_0.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ normative:
8080
RFC6749:
8181

8282
--- abstract
83-
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.
83+
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 profile 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.
8484

8585
Interoperability between SSF and CAEP, leveraging OAuth {{RFC6749}} provides greater assurance to implementers that their implementations will work out of the box with others.
8686

@@ -103,6 +103,9 @@ The following requirements are common across all use-cases defined in this docum
103103
* When using TLS 1.2, follow the recommendations for Secure Use of Transport Layer Security in [RFC7525]{{RFC7525}}.
104104
* The SSF receiver MUST perform a TLS server certificate signature checks, chain of trust validations, expiry and revocation status checks before calling the SSF transmitter APIs, as per [RFC6125]{{RFC6125}}.
105105

106+
## CAEP specification version
107+
This specification supports CAEP {{CAEP}} events from Implementer's Draft 1
108+
106109
## Transmitters {#common-transmitters}
107110
Transmitters MUST implement the following features:
108111

0 commit comments

Comments
 (0)