Skip to content

feat: support of Fortigate#827

Open
Manuthor wants to merge 3 commits intodevelopfrom
support/fortigate
Open

feat: support of Fortigate#827
Manuthor wants to merge 3 commits intodevelopfrom
support/fortigate

Conversation

@Manuthor
Copy link
Copy Markdown
Contributor

@Manuthor Manuthor commented Mar 24, 2026

Closes #824

@Manuthor Manuthor force-pushed the support/fortigate branch from eda7283 to 9c40e5e Compare March 30, 2026 09:48
@Manuthor Manuthor force-pushed the support/fortigate branch from c508275 to dc28fff Compare April 16, 2026 22:55
KMIP 1.0/1.1 clients such as FortiGate 40F (FortiOS 7.6) wrap their Locate
filter Attributes inside a TemplateAttribute structure in the RequestPayload
instead of placing them directly at the payload level (as KMIP 1.4 requires).

Without the new template_attribute field on kmip_1_4::Locate, the TTLV
deserializer silently discarded the TemplateAttribute wrapper, leaving
locate.attribute = None.  As a result, every Locate matched all objects owned
by the user and MaximumItems=1 always returned the same first key in the
database regardless of the requested Name filter.

Fix: add template_attribute: Option<TemplateAttribute> to kmip_1_4::Locate
and update the From<Locate> conversion to merge attributes from both sources
before building the KMIP 2.1 Attributes filter passed to the database layer.

Closes #824
@Manuthor Manuthor force-pushed the support/fortigate branch from dc28fff to fd4fc63 Compare April 17, 2026 05:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support FortiOS 7.6.0

1 participant