Closed aussietexan closed 1 year ago
@aussietexan , please try it with 0.6.11-beta and let us know if it is working for you.
Hi @fmunozmiranda. I tried using the same example code above to create the AuthC rule with the 0.6.11-beta code and now I get a 400 error.
│ Error: Failure when executing CreateNetworkAccessAuthenticationRule
│
│ with ciscoise_network_access_authentication_rules.mm-authc-eaptls,
│ on policy.tf line 309, in resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls":
│ 309: resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls" {
│
│ error with operation CreateNetworkAccessAuthenticationRule
│ {
│ "message" : "request has bad input format in the body",
│ "code" : 400
│ }
@fmunozmiranda. I noticed that the documentation was updated to included the 'condition_type' in the nested children block, so I updated my TF code as follows. It still returns the same 400 error.
TF Code
resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls" {
provider = ciscoise.ise31-2
parameters {
identity_source_name = ciscoise_id_store_sequence.iss-ad-cert.item[0].name
if_auth_fail = "REJECT"
if_process_fail = "DROP"
if_user_not_found = "REJECT"
policy_id = "8c73e8d8-1c3c-477b-8b6f-d58952d490f2"
rule {
default = "false"
name = var.authc-policy-eaptls
rank = 0
state = "enabled"
condition {
condition_type = "andBlock"
is_negate = "false"
children {
condition_type = "ConditionAttrs"
dictionary_name = "Radius"
attribute_name = "NAS-Port-Type"
operator = "equals"
attribute_value = "Ethernet"
is_negate = "false"
}
children {
condition_type = "ConditionAttrs"
dictionary_name = "Network Access"
attribute_name = "EapAuthentication"
operator = "equals"
attribute_value = "EAP-TLS"
is_negate = "false"
}
}
}
}
}
API body that returns 201 Created response
{
"rule": {
"default": false,
"name": "Dot1x EAP-TLS",
"rank": 0,
"state": "enabled",
"condition": {
"conditionType": "ConditionAndBlock",
"isNegate": false,
"children": [
{
"conditionType": "ConditionAttributes",
"isNegate": false,
"dictionaryName": "Radius",
"attributeName": "NAS-Port-Type",
"operator": "equals",
"attributeValue": "Ethernet"
},
{
"conditionType": "ConditionAttributes",
"isNegate": false,
"dictionaryName": "Network Access",
"attributeName": "EapAuthentication",
"operator": "equals",
"attributeValue": "EAP-TLS"
}
]
}
},
"identitySourceName": "ISS_AD_Cert",
"ifAuthFail": "REJECT",
"ifUserNotFound": "REJECT",
"ifProcessFail": "DROP"
}
Hi @aussietexan do you have a valid request body (functional on api, tested in postman or something like that) for this resource? if you have it, should you pass it?
Hi @fmunozmiranda , the response I posted above has an example request body for the API that returns a '201 Created' response when used in Postman.
Hey @aussietexan, I think the problem is in your condition_type
values it seems that accepted values are:
Could you tested with those changes?
Hi @fmunozmiranda , I updated my TF code to use those values rather than the values in the documentation (https://registry.terraform.io/providers/CiscoISE/ciscoise/latest/docs/resources/network_access_policy_set#nested-schema-for-parametersconditionchildren) and both the Policy Set and AuthC Policy resources worked correctly. Please update the documentation to reflect the correct accepted values.
Example TF code
resource "ciscoise_network_access_policy_set" "wired-mm-test" {
provider = ciscoise.ise31-2
depends_on = [
ciscoise_network_device_group.ndg_mm
]
parameters {
default = "false"
name = "Wired_MM_TEST"
description = "Wired Monitor Mode TEST"
rank = 0
is_proxy = "false"
service_name = "MAB_EAP-TLS"
state = "enabled"
condition {
condition_type = "ConditionAndBlock"
is_negate = "false"
children {
condition_type = "ConditionAttributes"
is_negate = "false"
dictionary_name = "Radius"
attribute_name = "NAS-Port-Type"
operator = "equals"
attribute_value = "Ethernet"
}
children {
condition_type = "ConditionAttributes"
is_negate = "false"
dictionary_name = "DEVICE"
attribute_name = "Deployment Stage"
operator = "equals"
attribute_value = "Deployment Stage#Monitor Mode"
}
}
}
}
resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls" {
provider = ciscoise.ise31-2
parameters {
identity_source_name = ciscoise_id_store_sequence.iss-ad-cert.item[0].name
if_auth_fail = "REJECT"
if_process_fail = "DROP"
if_user_not_found = "REJECT"
policy_id = ciscoise_network_access_policy_set.wired-mm-test.parameters[0].id
rule {
default = "false"
name = var.authc-policy-eaptls
rank = 0
state = "enabled"
condition {
condition_type = "ConditionAndBlock"
is_negate = "false"
children {
condition_type = "ConditionAttributes"
dictionary_name = "Radius"
attribute_name = "NAS-Port-Type"
operator = "equals"
attribute_value = "Ethernet"
is_negate = "false"
}
children {
condition_type = "ConditionAttributes"
dictionary_name = "Network Access"
attribute_name = "EapAuthentication"
operator = "equals"
attribute_value = "EAP-TLS"
is_negate = "false"
}
}
}
}
}
Thanks for feedback, I will update documentation in next realese.
Environment: ISE version and patch: ISE 3.1 patch 4 Terraform version: 1.3.1 ISE provider version: 0.6.10-beta OS version: MacOS 12.6
Affected resources The same nested logic described below should apply to all of the following resources:
Describe the bug The ISE Authentication and Authorization Policies support creation of multiple AND/OR condition matching blocks. As such, the TF resource needs to support creation of the same structure. When attempting to create a new AuthC Policy, TF return an error for multiple unsupported arguments:
Example code
OpenAPI call resulting in '201 Created' response
Additional context Policy Sets, Authentication, and Authorization policies support multiple levels of nesting, so the TF resources needs to support the same. Here is an example of the GET API output for a nested OR block within the same policy.