camaraproject/IdentityAndConsentManagement
Repository to describe, develop, document and test the Identity And Consent Management for CAMARA APIs
Apache-2.0
Pinned issues
Issues
- 5
- 7
Spring25: Proposal to RECOMMEND the use of Signed Request Object for the /authorize endpoint to prevent abuse
#205 opened by mhfoo - 11
- 12
Clarity on the use of login_hint
#191 opened by shilpa-padgaonkar - 8
Clarification for authentication in the auth code flow in the Identity and consent management (r0.20.0-rc2)
#199 opened by mingshiwork - 22
Allow to use operator_token (from TS43) to identify device on authentication request
#145 opened by Elisabeth-Ericsson - 16
- 12
- 9
Is the service API meant to validate the content of the access token and compare this against the API parameters ?
#174 opened by Elisabeth-Ericsson - 3
DPoP support in CAMARA OIDC Profile
#125 opened by gmuratk - 0
Generalize documents by using "API provider" rather than "Telco Operator"
#200 opened by tanjadegroot - 2
ICM text should not state that `Telco Operators` are the ones providing these APIs
#190 opened by RandyLevensalor - 2
- 2
SP supporting CIBA with two IDPs: B2B/B2C
#141 opened by questsin - 0
W3C Data Privacy Vocabulary (DPV) reference links in ICM documentation are broken
#195 opened by jpengar - 12
Review the APIs which are targeting "stable" maturity in the Fall24 meta-release
#189 opened by tanjadegroot - 6
- 4
- 23
Create ICM Release Plan
#146 opened by AxelNennker - 5
Replace internal links between ICM documents with relative links to stay within the same release tree / fork / release package
#187 opened by hdamker - 0
Link within mandatory text for all APIs points to main branch - need to be corrected in rc.2
#185 opened by hdamker - 7
OIDC authorization code flow and/or CIBA
#176 opened by AxelNennker - 0
SHADOW Add security to CAMARA_common.yaml
#164 opened by AxelNennker - 2
- 27
Proposal to protect the /authorize endpoint for the Authorization Code Flow (Auth Code Flow) - RFC9101
#128 opened by mhfoo - 10
Resolution on where the documentation of ICM AuthN/AuthZ common guidelines for API specs must be located
#160 opened by jpengar - 6
- 5
- 11
- 2
Fix statement about "missing sub claim" in case there is no id token
#156 opened by Elisabeth-Ericsson - 1
- 5
"CAMARA-API-access-and-user-consent.md" aligment with last decisions made in profile doc
#154 opened by jpengar - 11
Define a CIBA OpenAPI security scheme
#157 opened by AxelNennker - 0
Define behaviour and authentication mechanism for APIs not managing private information
#167 opened by jgarciahospital - 2
Explain or remove "3-legged" in CAMARA APIs access and user consent management
#159 opened by AxelNennker - 0
- 0
Update the Scope-section in ICM README.md
#149 opened by AxelNennker - 2
RFC7662 is mentioned twice in RFCs references list in Authentication and Authorization Concept for Service APIs
#161 opened by gregory1g - 12
- 0
Update and review of MAINTAINERS.MD file
#151 opened by hdamker - 7
Clarify role and usage of id token
#136 opened by Elisabeth-Ericsson - 11
Token Revocation if user revoked consent
#137 opened by AxelNennker - 17
- 6
Clarify on the need of optional claims in CIBA Client Authentication request.
#132 opened by shilpa-padgaonkar - 6
Clarification needed for login_hint, login_hint_token and id_token_hint
#133 opened by shilpa-padgaonkar - 11
Camara Identity Profile the way forward
#122 opened by AxelNennker - 2
Consent api spec
#142 opened by questsin - 2
- 26
- 15