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
The following endpoints are only reachable via the "Onboarding Service Provider Management" Page.
Therefor the permission needs to be adjusted accordingly
Adjust the following endpoint to verify against the permission configure_partner_registration
move api/administration/registration/network/companies to network controller
api/administration/registration/network/companies -> should be moved to the network controller
Acceptance Criteria
Ensure that the endpoints POST: api/administration/registration/network/partnerRegistration and GET: api/administration/registration/network/companies are only accessible to users who have the configure_partner_registration permission.
Unauthorized access attempts should return an appropriate HTTP status code indicating lack of permission (e.g., 403 Forbidden).
Move the GET: api/administration/registration/network/companies endpoint from its current controller to the network controller.
Test cases
Authorized Access - POST Endpoint
Objective: Verify that a user with configure_partner_registration permission can access the POST: api/administration/registration/network/partnerRegistration endpoint. Steps:
Authenticate as a user with configure_partner_registration permission.
Send a POST request to api/administration/registration/network/partnerRegistration. Expected Result: The request is successful, and the server responds with a 200 OK status code.
Unauthorized Access - POST Endpoint
Objective: Ensure that a user without configure_partner_registration permission receives a 403 Forbidden status when attempting to access the POST: api/administration/registration/network/partnerRegistration endpoint. Steps:
Authenticate as a user without configure_partner_registration permission.
Send a POST request to api/administration/registration/network/partnerRegistration. Expected Result: The server responds with a 403 Forbidden status code.
Authorized Access - GET Endpoint
Objective: Confirm that a user with configure_partner_registration permission can access the GET: api/administration/registration/network/companies endpoint. Steps:
Authenticate as a user with configure_partner_registration permission.
Send a GET request to api/administration/registration/network/companies. Expected Result: The request is successful, and the server responds with a 200 OK status code.
Unauthorized Access - GET Endpoint
Objective: Verify that a user without configure_partner_registration permission receives a 403 Forbidden status when attempting to access the GET: api/administration/registration/network/companies endpoint. Steps:
Authenticate as a user without configure_partner_registration permission.
Send a GET request to api/administration/registration/network/companies. Expected Result: The server responds with a 403 Forbidden status code.
The text was updated successfully, but these errors were encountered:
MaximilianHauer
changed the title
sig#809 - Implement Companyrole based policy-types
sig#809 - Implement permission for Onboarding Service Provider endpoints
Sep 12, 2024
* relocate endpoint api/administration/registration/network/companies to api/administration/network/companies
* adjust permisssion from 'view_submitted_applications' to 'configure_partner_registration'
Refs: #994
Description
The following endpoints are only reachable via the "Onboarding Service Provider Management" Page.
Therefor the permission needs to be adjusted accordingly
Adjust the following endpoint to verify against the permission
configure_partner_registration
POST: api/administration/registration/network/partnerRegistration
GET: api/administration/registration/network/companies
move api/administration/registration/network/companies to network controller
api/administration/registration/network/companies -> should be moved to the network controller
Acceptance Criteria
POST: api/administration/registration/network/partnerRegistration
andGET: api/administration/registration/network/companies
are only accessible to users who have theconfigure_partner_registration
permission.Test cases
Authorized Access - POST Endpoint
Objective: Verify that a user with
configure_partner_registration
permission can access thePOST: api/administration/registration/network/partnerRegistration
endpoint.Steps:
Authenticate as a user with
configure_partner_registration
permission.Send a
POST
request toapi/administration/registration/network/partnerRegistration
.Expected Result: The request is successful, and the server responds with a 200 OK status code.
Unauthorized Access - POST Endpoint
Objective: Ensure that a user without
configure_partner_registration
permission receives a 403 Forbidden status when attempting to access thePOST: api/administration/registration/network/partnerRegistration
endpoint.Steps:
Authenticate as a user without
configure_partner_registration
permission.Send a POST request to
api/administration/registration/network/partnerRegistration
.Expected Result: The server responds with a 403 Forbidden status code.
Authorized Access - GET Endpoint
Objective: Confirm that a user with configure_partner_registration permission can access the
GET: api/administration/registration/network/companies endpoint
.Steps:
Authenticate as a user with
configure_partner_registration
permission.Send a GET request to
api/administration/registration/network/companies
.Expected Result: The request is successful, and the server responds with a 200 OK status code.
Unauthorized Access - GET Endpoint
Objective
: Verify that a user withoutconfigure_partner_registration
permission receives a 403 Forbidden status when attempting to access theGET: api/administration/registration/network/companies endpoint
.Steps
:Authenticate as a user without configure_partner_registration permission.
Send a GET request to
api/administration/registration/network/companies
.Expected Result
: The server responds with a 403 Forbidden status code.The text was updated successfully, but these errors were encountered: