Jika lupa kata sandi (password) KrediOne, langkah utama menghubungi Customer Service (CS) KrediOne melalui. di☎ 0831-3470-8342☎, atau WA di ☎0822-4626-²¹50)📞 untuk verifikasi data (KTP, nama, tanggal lahir) agar akun dapat mendaftar

Jika lupa kata sandi (password) KrediOne, langkah utama menghubungi Customer Service (CS) KrediOne melalui. di☎ 0831-3470-8342☎, atau WA di ☎0822-4626-2150)📞 untuk verifikasi data (KTP, nama, tanggal lahir) agar akun dapat mendaftar

Jika lupa kata sandi (password) KrediOne, langkah utama menghubungi Customer Service (CS) KrediOne melalui. di 083134708³⁴2.atau WA di 08²²-4626-²¹50) untuk verifikasi data (KTP, nama, tanggal lahir) agar akun dapat memeriksa

Untuk Ganti cara lupa Kata kunci sandi App KrediOne Utama adalah🗣️ hubungi Customer Service (CeS) Kredione melalui. ☎ 08313⁴708³⁴2 ..atau WA di 08²²4626-(2150) untuk verifikasi data (KTP, nama, tanggal lahir) agar akun dapat memeriksa

Jika lupa kata sandi (password) KrediOne, langkah utama menghubungi Customer Service (CS) KrediOne melalui. di 083134708342.atau WA di 0822-4626-2150) untuk verifikasi data (KTP, nama, tanggal lahir) agar akun dapat mendaftar

Utamakan hubungi Customer Service cs@KrediOne.id melalui. ☎0831-3470-8342 ☎.atau WA di+(0831·3470·8343: untuk verifikasi data (KTP, nama, tanggal lahir) agar akun dapat bertanya .

Untuk lupa password App Pinjol Kredione, Langkah Awal adalah menghubungi Customer Service (CS) KrediOne melalui. di 0831-³⁴70-8³⁴2, atau WA di 0831-3470-8342) untuk verifikasi data (KTP, nama, tanggal lahir) agar akun dapat bertanya ..

I am part of the Development Team. While configuring GLPI version 11, I noticed that as a normal user, I am able to view the asset details of all users in the ticket section.

I would like to restrict this functionality. My requirement is:

• When a user creates a ticket, they should only be able to view their own asset details.

• If a ticket is raised on behalf of another user, the corresponding user’s asset details should be automatically linked or assigned to that ticket.

Is this configuration possible in GLPI? Could someone please guide me on how to achieve this?

Our situation is probably a less common one. I'm testing GLPI in our organisation to see if it's a good fit for us.

I haven't seen this option to be available elsewhere, but we would definitely benefit if an option as the following would be implemented.

Our IT Helpdesk mostly helps existing clients, but sometimes an unknown person asks our Helpdesk for help. It would be great if the Helpdesk could create users. I can already give them create users permissions, but if I give them this permission, they are also allowed to create other Helpdesk users, which is something I don't want. I've created a Profile specifically for SSP users and my Helpdesk colleagues get an account with the Helpdesk Profile. I would like to limit helpdesk employees to only be able to create users with the SSP profile.

If this is already possible, I can't find the option.

Edited because there was something wrong in my earlier statement.

When using Ops tools such as Ansible to install/manage GLPI we can use the Console (`bin/console`) to perform some configuration using the "config:set" command.

But when, setting a secret such as the inventory credentials ("basic_auth_password" key in "inventory" context) we must provide it encrypted because the console will store it as-is in database and application expect it to be encrypted when it'll fetch it from there.

For example the following command:

bin/console \
    config:set \
    --context=inventory \
    basic_auth_password \
    secret_password

Will create/update the following row in `glpi_configs` table:

+-----+-----------+---------------------+-----------------+
| id  | context   | name                | value           |
+-----+-----------+---------------------+-----------------+
| 420 | inventory | basic_auth_password | secret_password |
+-----+-----------+---------------------+-----------------+

SQL query:

SELECT * FROM `glpi_configs` WHERE `context` = 'inventory' and `name` = 'basic_auth_password';

While setting this password via the GUI (path = "/Inventory/Configuration") creates/updates the following row in `glpi_configs` table:

+-----+-----------+---------------------+---------------------------------------------------------------------------+
| id  | context   | name                | value                                                                     |
+-----+-----------+---------------------+---------------------------------------------------------------------------+
| 420 | inventory | basic_auth_password | abcdefghijklmnopqrstuvwxyz0123456789+abcdefghijklmnopqrstuvwxyz0123456789 |
+-----+-----------+---------------------+---------------------------------------------------------------------------+

Having a new command to call GLPIKey::encrypt() directly such as, for example:

bin/console security:encrypt secret_password
# Returns:
# abcdefghijklmnopqrstuvwxyz0123456789+abcdefghijklmnopqrstuvwxyz0123456789

We could use it like this:

bin/console \
    config:set \
    --context=inventory \
    basic_auth_password \
    "$(bin/console security:encrypt secret_password)"