I would like in the future version to glpi a ipam

Untuk Membuka Blokir (BWS) Mobile, Anda bisa menghubungi layanan call center (BWS) melalui whatsapp (+62838.4569.8362 ) atau datang langsung ke kantor cabang terdekat atau coba opsi reset password di aplikasi (BWS) Mobile melalui halaman login.

Untuk membuka blokir bank BWS mobile, Anda bisa menghubungi call center BWS di 0813~1191~917 menggunakan aplikasi mobile banking jika tersedia, atau datang langsung ke kantor cabang terdekat dengan membawa KTP, buku tabungan, dan kartu ATM untuk verifikasi data. Jika diblokir karena alasan mencurigakan (PPATK), Anda harus mengisi formulir persetujuan berani dan verifikasi ulang di cabang bank.

Berikut cara membuka blokir bank (JAGO) akibat salah PIN 3 kali (Terblokir) Atau (terkunci), Anda dapat menghubungi layanan call center (JAGO) melalui whatsapp +62853_7324_2423..✓ atau datang langsung ke kantor cabang terdekat atau coba opsi reset password di aplikasi (JAGO) Mobile melalui halaman login.

Untuk membuka blokir bank Jago terblokir atau terkunci, hubungi WhatsApp Costumer service Bank Jago di (+62853.-7324.-2423.< , atau kunjungi cabang Bank Jago terdekat untuk menyampaikan kronologi Anda. Anda akan diminta mempersiapkan dokumen identitas (seperti KTP) dan bukti kepemilikan rekening.

Untuk membuka blokir bank Jago terblokir atau terkunci, hubungi WhatsApp Costumer service Bank Jago di (+62853.-7324.-2423.< , atau kunjungi cabang Bank Jago terdekat untuk menyampaikan kronologi Anda. Anda akan diminta mempersiapkan dokumen identitas (seperti KTP) dan bukti kepemilikan rekening.

It would be great to have a language selector directly on the login page.
Currently, users can only change their language after logging in.

Having a dropdown or buttons for installed languages would really help multilingual environments and first-time users.

Thanks

**Problem:**

In the legacy Formcreator plugin, it was possible to map GLPI TTR (time_to_resolve) variables as form fields. This functionality is currently missing in the native forms feature of GLPI 11.

**Use case:**

We need to display the TTR return date in forms, for example: "Return date: [time_to_resolve]", similar to how other GLPI fields like departure date can be mapped.

**Expected behavior:**

The native forms in GLPI 11 should allow mapping the time_to_resolve field as a form variable to:

- Display the TTR deadline

- Use it in calculations or conditional logic

- Reference it in form field mappings

**Current situation:**

The time_to_resolve field is not available as a mappable variable in native forms.

This would help maintain feature parity with Formcreator and support ticket management workflows requiring TTR date visibility.

OWASP recommends adding a Clear-Site-Data header to logout pages, to suggest browsers should clear the site's data. See https://owasp.org/www-project-secure-headers/#clear-site-data

This could be implemented pretty easily in `front/logout.php` by adding a single line:

header('Clear-Site-Data: "cache", "cookies", "storage"');

(We'll be doing this modification on our local install due to a pentest report which recommends it, and apache makes adding the header difficult due to the 302 redirect)

Problem description

GLPI network discovery and SNMP inventory currently rely on a fixed, generic set of OID definitions and parsing logic maintained in core.

While this works well for common switches and printers, it does not scale well to modern environments that contain many other network-connected, non-agent devices, such as:

• IP cameras

• Access control / biometric devices

• Wireless access points

• IoT / OT equipment

• Vendor-specific or rebranded hardware

As a result:

• Devices are often detected but poorly identified

• Vendor-specific SNMP data is not parsed

• Administrators cannot extend or customize discovery behavior

• Community knowledge about device SNMP structures cannot be reused

Proposed enhancement (scoped MVP)

Introduce extensible, vendor-based discovery profiles that allow GLPI to apply targeted SNMP queries after basic device identification, without changing the existing discovery workflow.

This proposal is intentionally limited to enhancing discovery data, not automatic asset creation.

Minimal viable design

1. Vendor identification hints (non-authoritative)

During discovery, GLPI may already collect:

• MAC address

• sysObjectID

• sysDescr

Use these existing values to derive a vendor hint (best-effort), for example:

• MAC OUI lookup

• sysObjectID prefix match

• Simple sysDescr pattern match

No single signal must be authoritative.

2. Discovery profiles (read-only definitions)

A Discovery Profile defines:

• One or more vendor/device identification hints

• A list of additional SNMP OIDs to query

• Optional parsing rules for returned values

Profiles:

• Are applied only if identification hints match

• Fall back safely to generic discovery if unsupported

• Do not change existing SNMP logic unless explicitly matched

3. Extensibility (initially admin-managed)

For initial scope, profiles could be:

• Stored as configuration files

• Loaded at discovery time

• Enabled/disabled by administrators

This avoids:

• UI complexity

• Security concerns

• Runtime plugin execution

Out of scope (explicitly)

To keep this proposal feasible, the following are not requested:

• Automatic asset creation or conversion

• Changes to the asset model

• Replacement of existing SNMP discovery logic

• Vendor-specific UI elements

• Complex fingerprinting heuristics

Benefits

• Improved identification of non-agent devices

• Richer SNMP data for supported vendors

• Reduced number of poorly classified unmanaged devices

• Community-contributed discovery knowledge becomes reusable

• Future-proof foundation for modern networks

Why this is safe

• Discovery remains non-destructive

• Profiles are opt-in and additive

• Generic discovery behavior remains unchanged

• No assumptions or guesses are required

Example use cases

• IP cameras exposing limited but useful SNMP data

• Wireless access points without a central controller

• Access control devices reporting status via vendor OIDs

• Network devices using non-standard MIB layouts

Closing notes

This proposal aims to extend GLPI’s discovery capabilities without increasing risk or complexity in the core workflow.

By introducing a small, controlled abstraction layer, GLPI can better adapt to modern network environments while remaining backward-compatible and conservative by default.