Skip to content

Assign ownership of AuthN Mappings to Identity/User | ACCESS-3549 #2651

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+15 −15
Open

Assign ownership of AuthN Mappings to Identity/User | ACCESS-3549 #2651

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .generated-info
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
{
"spec_repo_commit": "c38287b",
"generated": "2025-08-15 18:55:02.903"
"spec_repo_commit": "46f96e9",
"generated": "2025-08-15 21:03:10.563"
}
26 changes: 13 additions & 13 deletions features/v2/authn_mappings.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,21 +10,21 @@ Feature: AuthN Mappings
And a valid "appKeyAuth" key in the system
And an instance of "AuthNMappings" API

@generated @skip @team:DataDog/aaa-core-access
@generated @skip @team:DataDog/team-aaa-identity
Scenario: Create an AuthN Mapping returns "Bad Request" response
Given new "CreateAuthNMapping" request
And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}}
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/aaa-core-access
@generated @skip @team:DataDog/team-aaa-identity
Scenario: Create an AuthN Mapping returns "Not Found" response
Given new "CreateAuthNMapping" request
And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}}
When the request is sent
Then the response status is 404 Not Found

@team:DataDog/aaa-core-access
@team:DataDog/team-aaa-identity
Scenario: Create an AuthN Mapping returns "OK" response
Given there is a valid "role" in the system
And new "CreateAuthNMapping" request
Expand All @@ -35,14 +35,14 @@ Feature: AuthN Mappings
And the response "data.attributes.attribute_value" is equal to "{{ unique }}"
And the response "data.relationships.role.data.id" is equal to "{{ role.data.id }}"

@generated @skip @team:DataDog/aaa-core-access
@generated @skip @team:DataDog/team-aaa-identity
Scenario: Delete an AuthN Mapping returns "Not Found" response
Given new "DeleteAuthNMapping" request
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not Found

@team:DataDog/aaa-core-access
@team:DataDog/team-aaa-identity
Scenario: Delete an AuthN Mapping returns "OK" response
Given there is a valid "role" in the system
And there is a valid "authn_mapping" in the system
Expand All @@ -51,31 +51,31 @@ Feature: AuthN Mappings
When the request is sent
Then the response status is 204 OK

@generated @skip @team:DataDog/aaa-core-access
@generated @skip @team:DataDog/team-aaa-identity
Scenario: Edit an AuthN Mapping returns "Bad Request" response
Given new "UpdateAuthNMapping" request
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}}
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/aaa-core-access
@generated @skip @team:DataDog/team-aaa-identity
Scenario: Edit an AuthN Mapping returns "Conflict" response
Given new "UpdateAuthNMapping" request
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}}
When the request is sent
Then the response status is 409 Conflict

@generated @skip @team:DataDog/aaa-core-access
@generated @skip @team:DataDog/team-aaa-identity
Scenario: Edit an AuthN Mapping returns "Not Found" response
Given new "UpdateAuthNMapping" request
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}}
When the request is sent
Then the response status is 404 Not Found

@team:DataDog/aaa-core-access
@team:DataDog/team-aaa-identity
Scenario: Edit an AuthN Mapping returns "OK" response
Given there is a valid "role" in the system
And there is a valid "authn_mapping" in the system
Expand All @@ -89,22 +89,22 @@ Feature: AuthN Mappings
And the response "data.attributes.attribute_value" is equal to "Development"
And the response "data.relationships.role.data.id" is equal to "{{ role.data.id }}"

@generated @skip @team:DataDog/aaa-core-access
@generated @skip @team:DataDog/team-aaa-identity
Scenario: Edit an AuthN Mapping returns "Unprocessable Entity" response
Given new "UpdateAuthNMapping" request
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}}
When the request is sent
Then the response status is 422 Unprocessable Entity

@generated @skip @team:DataDog/aaa-core-access
@generated @skip @team:DataDog/team-aaa-identity
Scenario: Get an AuthN Mapping by UUID returns "Not Found" response
Given new "GetAuthNMapping" request
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not Found

@team:DataDog/aaa-core-access
@team:DataDog/team-aaa-identity
Scenario: Get an AuthN Mapping by UUID returns "OK" response
Given there is a valid "role" in the system
And there is a valid "authn_mapping" in the system
Expand All @@ -117,7 +117,7 @@ Feature: AuthN Mappings
And the response "data.attributes.attribute_value" is equal to "{{ unique }}"
And the response "data.relationships.role.data.id" is equal to "{{ role.data.id }}"

@team:DataDog/aaa-core-access
@team:DataDog/team-aaa-identity
Scenario: List all AuthN Mappings returns "OK" response
Given there is a valid "role" in the system
And there is a valid "authn_mapping" in the system
Expand Down