Hi,
On FortiSIEM 7.3.2, I cannot create an SNMPv3 credential, I always get the following error: Save failed - invalid characters (`, $, >, <, &, ;, |) found
Has anyone encountered this error? What could be the problem?
Thanks,
Zoltan
on fortisiem 7.3.2?
No, I mean FSM 7.2.5.
BTW that's why you should always install mature releases in your production env.
Wow. Unlike in fortigate, I don't see feature and mature releases in fortisiem.
How do you know which ones you can use and which ones you can't? On the other hand, the suggestion is to always use the latest patch.
I think this is a bug in 7.3.2, and the solution is not to use 7.2.x...
First of all let's see what 7.3.2 means (probably you already know):
But you are right. Some Fortinet products, like FSM, don't mention if the product is mature or not yet.
How do I know if it is mature or not? Just by looking to the patch number. If it is somewhere below 5 or 6 then it is probably not mature yet. But this is just an approximation from to my experience.
So in this case, if I have to install FSM for my production env, I'd go for 7.2.6 instead of 7.3.2, where 7.2.6 is currently the latest patch of the 7.2 release. An so far it works great, I'm not affected by the most know/unknown bugs.
And why would I install 7.3.2? Only if there is a great new feature (check release notes) that I absolutely need for my environment, in that case I may sacrifice the stability for that very important new feature, otherwise I don't.
And why I'd drop 7.2.x for a higher release? If the 7.2.x will be EoS soon, because there will be no patches anymore.
OK! I think differently but I accept yours too :)
I'm experiencing the same issue on FortiSIEM 7.3.2.0374 — trying to save an SNMPv3 access method throws a "Save failed - invalid characters" error even when using clean and valid values without any special characters. I've tested with multiple browsers, different keyboard layouts, and manually typed inputs, but the validation still fails. This appears to be a frontend validation bug in the SNMPv3 config form. You're not alone — hope Fortinet patches this soon.
Created on 04-14-2025 07:36 AM Edited on 04-14-2025 07:36 AM
Hi @yans ,
I couldn't find any existing mantis for this issue. Please open a TAC ticket to push for a fix of this issue.
I did it two weeks ago, ticket number:
Regards,
Zoltan
Hi @rz5 ,
I can see the TAC couldn't replicate this issue in the ticket.
If I were the TAC, I would schedule a call to record the session with what you would show the issue, then report a bug with this recording.
It's very easy to replicate the issue, I don't understand what's going on there.
I currently have two deployments running the same version mentioned above and I am hitting the same bug in both of them.
Welcome to your new Fortinet Community!
You'll find your previous forum posts under "Forums"
User | Count |
---|---|
72 | |
25 | |
15 | |
10 | |
10 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.