You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, GET /v3/organizations returns the full list of organizations present on the foundation. We should only return the organizations the user making the request belongs to, e.g. organizations the user has some role in.
We want to keep this behaviour behind a feature flag for now, to avoid having a mix of authenticated and unauthenticated endpoints exposed.
Acceptance Criteria
GIVEN a cf root namespace exists AND the org1, org2 and org3 subnamespaces of cf exist ANDuser has RoleBindings (to any role for now) in org1 and org3 AND a token issued to user exists WHENuser performs a GET /v3/organizations including the Authorization: ClientCert <the-client-cert-and-key> header THEN they only see org1 and org3 in the resources field
GIVEN a cf root namespace exists AND the org1, org2 and org3 subnamespaces of cf exist ANDuser has RoleBindings (to any role for now) in org1 and org3 WHENuser performs a GET /v3/organizations without the Authorization header THEN they get a 401 Unauthorized response with a NotAuthenticated error message
Dev Notes
Possible formats for the header:
Authorization: ClientCert XXX/YYY
Authorization: ClientCert XXX ClientKey YYY
The text was updated successfully, but these errors were encountered:
When auth uses the ClientCert type, the identity provider can get the
username by decoding the passed client certificate and extracting the
common name from the subject
Issue: #168
Co-authored-by: Giuseppe Capizzi <gcapizzi@pivotal.io>
When auth uses the ClientCert type, the identity provider can get the
username by decoding the passed client certificate and extracting the
common name from the subject
Issue: #168
Co-authored-by: Giuseppe Capizzi <gcapizzi@pivotal.io>
Background
At the moment,
GET /v3/organizations
returns the full list of organizations present on the foundation. We should only return the organizations the user making the request belongs to, e.g. organizations the user has some role in.We want to keep this behaviour behind a feature flag for now, to avoid having a mix of authenticated and unauthenticated endpoints exposed.
Acceptance Criteria
GIVEN a
cf
root namespace existsAND the
org1
,org2
andorg3
subnamespaces ofcf
existAND
user
hasRoleBinding
s (to any role for now) inorg1
andorg3
AND a token issued to
user
existsWHEN
user
performs aGET /v3/organizations
including theAuthorization: ClientCert <the-client-cert-and-key>
headerTHEN they only see
org1
andorg3
in theresources
fieldGIVEN a
cf
root namespace existsAND the
org1
,org2
andorg3
subnamespaces ofcf
existAND
user
hasRoleBinding
s (to any role for now) inorg1
andorg3
WHEN
user
performs aGET /v3/organizations
without theAuthorization
headerTHEN they get a
401 Unauthorized
response with aNotAuthenticated
error messageDev Notes
Authorization: ClientCert XXX/YYY
Authorization: ClientCert XXX ClientKey YYY
The text was updated successfully, but these errors were encountered: