Skip to content

Conversation

@jischr
Copy link
Contributor

@jischr jischr commented Apr 1, 2025

Fixes #203

I took a stab at this one as best as I could understand the issue and profile. Happy to rework the wording if it isn't quite right.

@jischr jischr requested a review from a team as a code owner April 1, 2025 01:36
@FragLegs
Copy link
Contributor

FragLegs commented Apr 1, 2025

@apoorvadeshpande-okta and @jischr to chat about combining PRs

Copy link
Contributor

@appsdesh appsdesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! looks good

@jischr
Copy link
Contributor Author

jischr commented Apr 1, 2025

@FragLegs or @iamseanodentity can you take another look?

@tulshi tulshi added the v1Final Issues that must be fixed before we propose a spec to become a v1 final spec. label Apr 22, 2025
@tulshi
Copy link
Contributor

tulshi commented Apr 24, 2025

We are not considering making the "CAEP Interoperability profile" a final spec in this round, so I will drop the "v1Final" label on this issue.

@tulshi tulshi added vFuture and removed v1Final Issues that must be fixed before we propose a spec to become a v1 final spec. labels Apr 24, 2025
@tulshi tulshi added the spec:Interop Issues with the interop spec. label Dec 5, 2025
@derrumbe derrumbe merged commit 4b238c9 into openid:main Dec 19, 2025
2 checks passed
@jischr jischr deleted the issue203 branch December 19, 2025 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

spec:Interop Issues with the interop spec. vFuture

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Section 2.7.1 in the CAEP Interop spec is confusing

5 participants