Adding custom vulnerability signature via API fails with 'API_I00013' and 'qualifier is invalid'
1269
Created On 11/12/24 00:13 AM - Last Modified 10/22/25 18:52 PM
Symptom
Adding a custom vulnerability signature via API fails with the following error only when adding a qualifier to the request.
{
"_errors": [
{
"code": "API_I00013", <<<<<<<<<<<<<!!!
"message": "設定が無効です。詳細についてはエラー メッセージを確認してください。",
"details": {
"errorType": "Invalid Object",
"message": [
" 42005 -> signature -> standard -> TEST -> and-condition -> And Condition 1 -> or-condition -> Or Condition 1 -> operator -> pattern-match -> qualifier -> value has unexpected text.",
" 42005 -> signature -> standard -> TEST -> and-condition -> And Condition 1 -> or-condition -> Or Condition 1 -> operator -> pattern-match -> qualifier is invalid" <<<<<<<<<<<<< !!!
],
"errors": [
{
"type": "UNEXPECTED_TEXT_ERR",
"message": "node has unexpected text",
"params": [
"value"
]
}
]
}
}
],
"_request_id": "xxxx-xxxx-xxxx-xxxx-xxxxxxxxxx"
}Environment
- Prisma Access API
Resolution
This will be fixed in SCM version 2025.r1.0, which is currently scheduled for Mid Feb 2025.
The SCM version can be verified under SCM > Manage > Configuration > NGFW and Prisma Access > Configuration Scope: Global > General Information > Cloud Management Version.