Solved: Security Gateway name cannot start with "in-"

Hi,

maybe it is written somewhere in the documentation I couldn't find.

It seems that a new gateway object can't start with the combination "in-".

The error message reads: "Token includes a reserved word".
Is there a specific reason for that?

I know it's just cosmetic but it kind breaks our naming concept.

_Val_ · ‎2024-09-16

From the same SK, in is a reserved word and cannot be used.

AkosBakos · ‎2024-09-16

Here is the link of the banned words:

But I haven't found the "in-" prefix in the SK

Akos

----------------
\m/_(>_<)_\m/

_Val_ · ‎2024-09-16

From the same SK, in is a reserved word and cannot be used.

AkosBakos · ‎2024-09-16

ohh, I need to visit my optician 🙂

----------------
\m/_(>_<)_\m/

bernhard_ertl · ‎2024-09-16

Thank you Val,

it seems a bit inconsistent, because "in-" wasn't allowed but "in_" is allowed as prefix to a hostname.

but thanks for pointing out the proper SK.

cheers

the_rock · ‎2024-09-16

Thats right, I just tested same in R82, exact same behavior.

Andy

Best,
Andy
"Have a great day and if its not, change it"

Are you a member of CheckMates?