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
Copy file name to clipboardExpand all lines: tests/v2/features/authn_mappings.feature
+13-13Lines changed: 13 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -10,21 +10,21 @@ Feature: AuthN Mappings
10
10
And a valid "appKeyAuth" key in the system
11
11
And an instance of "AuthNMappings" API
12
12
13
-
@generated@skip@team:DataDog/aaa-core-access
13
+
@generated@skip@team:DataDog/team-aaa-identity
14
14
Scenario: Create an AuthN Mapping returns "Bad Request" response
15
15
Given new "CreateAuthNMapping" request
16
16
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"}}
17
17
When the request is sent
18
18
Then the response status is 400 Bad Request
19
19
20
-
@generated@skip@team:DataDog/aaa-core-access
20
+
@generated@skip@team:DataDog/team-aaa-identity
21
21
Scenario: Create an AuthN Mapping returns "Not Found" response
22
22
Given new "CreateAuthNMapping" request
23
23
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"}}
24
24
When the request is sent
25
25
Then the response status is 404 Not Found
26
26
27
-
@team:DataDog/aaa-core-access
27
+
@team:DataDog/team-aaa-identity
28
28
Scenario: Create an AuthN Mapping returns "OK" response
29
29
Given there is a valid "role" in the system
30
30
And new "CreateAuthNMapping" request
@@ -35,14 +35,14 @@ Feature: AuthN Mappings
35
35
And the response "data.attributes.attribute_value" is equal to "{{ unique }}"
36
36
And the response "data.relationships.role.data.id" is equal to "{{ role.data.id }}"
37
37
38
-
@generated@skip@team:DataDog/aaa-core-access
38
+
@generated@skip@team:DataDog/team-aaa-identity
39
39
Scenario: Delete an AuthN Mapping returns "Not Found" response
40
40
Given new "DeleteAuthNMapping" request
41
41
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
42
42
When the request is sent
43
43
Then the response status is 404 Not Found
44
44
45
-
@team:DataDog/aaa-core-access
45
+
@team:DataDog/team-aaa-identity
46
46
Scenario: Delete an AuthN Mapping returns "OK" response
47
47
Given there is a valid "role" in the system
48
48
And there is a valid "authn_mapping" in the system
@@ -51,31 +51,31 @@ Feature: AuthN Mappings
51
51
When the request is sent
52
52
Then the response status is 204 OK
53
53
54
-
@generated@skip@team:DataDog/aaa-core-access
54
+
@generated@skip@team:DataDog/team-aaa-identity
55
55
Scenario: Edit an AuthN Mapping returns "Bad Request" response
56
56
Given new "UpdateAuthNMapping" request
57
57
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
58
58
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"}}
59
59
When the request is sent
60
60
Then the response status is 400 Bad Request
61
61
62
-
@generated@skip@team:DataDog/aaa-core-access
62
+
@generated@skip@team:DataDog/team-aaa-identity
63
63
Scenario: Edit an AuthN Mapping returns "Conflict" response
64
64
Given new "UpdateAuthNMapping" request
65
65
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
66
66
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"}}
67
67
When the request is sent
68
68
Then the response status is 409 Conflict
69
69
70
-
@generated@skip@team:DataDog/aaa-core-access
70
+
@generated@skip@team:DataDog/team-aaa-identity
71
71
Scenario: Edit an AuthN Mapping returns "Not Found" response
72
72
Given new "UpdateAuthNMapping" request
73
73
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
74
74
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"}}
75
75
When the request is sent
76
76
Then the response status is 404 Not Found
77
77
78
-
@team:DataDog/aaa-core-access
78
+
@team:DataDog/team-aaa-identity
79
79
Scenario: Edit an AuthN Mapping returns "OK" response
80
80
Given there is a valid "role" in the system
81
81
And there is a valid "authn_mapping" in the system
@@ -89,22 +89,22 @@ Feature: AuthN Mappings
89
89
And the response "data.attributes.attribute_value" is equal to "Development"
90
90
And the response "data.relationships.role.data.id" is equal to "{{ role.data.id }}"
91
91
92
-
@generated@skip@team:DataDog/aaa-core-access
92
+
@generated@skip@team:DataDog/team-aaa-identity
93
93
Scenario: Edit an AuthN Mapping returns "Unprocessable Entity" response
94
94
Given new "UpdateAuthNMapping" request
95
95
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
96
96
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"}}
97
97
When the request is sent
98
98
Then the response status is 422 Unprocessable Entity
99
99
100
-
@generated@skip@team:DataDog/aaa-core-access
100
+
@generated@skip@team:DataDog/team-aaa-identity
101
101
Scenario: Get an AuthN Mapping by UUID returns "Not Found" response
102
102
Given new "GetAuthNMapping" request
103
103
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
104
104
When the request is sent
105
105
Then the response status is 404 Not Found
106
106
107
-
@team:DataDog/aaa-core-access
107
+
@team:DataDog/team-aaa-identity
108
108
Scenario: Get an AuthN Mapping by UUID returns "OK" response
109
109
Given there is a valid "role" in the system
110
110
And there is a valid "authn_mapping" in the system
@@ -117,7 +117,7 @@ Feature: AuthN Mappings
117
117
And the response "data.attributes.attribute_value" is equal to "{{ unique }}"
118
118
And the response "data.relationships.role.data.id" is equal to "{{ role.data.id }}"
119
119
120
-
@team:DataDog/aaa-core-access
120
+
@team:DataDog/team-aaa-identity
121
121
Scenario: List all AuthN Mappings returns "OK" response
122
122
Given there is a valid "role" in the system
123
123
And there is a valid "authn_mapping" in the system
0 commit comments