Automatically binding credentials

Post your feature requests here
Post Reply
cinio
Posts: 2
Joined: Tue Feb 27, 2024 3:57 pm

Mon Oct 14, 2024 11:14 am

I'm looking for an option to be able to set "automatic credentials binding" feature.

I'd imagine it should work like that: during device discovery, once all credentials are checked, the pair which allowed access to device should be bind automatically.

Currently credentials which worked on device have this fact displayed in "Credentials" menu in "Used by device" column and whole list of devices for which those credentials are valid can be seen in "Show usage" submenu.
Unfortunately it's impossible to automatically bind those credentials to those devices, and that's the feature I would like to see in the future releases.

Thanks.
erik.k
Posts: 40
Joined: Wed Feb 07, 2024 8:16 am

Tue Oct 15, 2024 7:18 am

Hi, thank you for your post.

We received similar requirements in the past, and they are already documented in our backlog. Unfortunately, no ETA has been provided for this topic yet, but I will let you know if there are any updates.
gt732
Posts: 7
Joined: Tue Aug 15, 2023 7:13 pm

Fri May 22, 2026 12:36 pm

what is the workaround for now? I'm also running into this issue, tons of failed logins during the scheduled backup when unimus already knows which credential pair works when it did the discovery before.
Tommy.c
Posts: 72
Joined: Fri Jan 31, 2025 6:52 pm

Tue Jun 09, 2026 1:46 pm

There are three workarounds that I know of.

Manually binding the credentials for each device.

Having a single set of credentials that Unimus utilizes. (this is my preference)

Editing the Database, you can manually edit the DB. (This is easier with the non-HSQL DBs) and bind credentials from there. If you are wanting to programmatically bind credentials this is the recommended method to do so at scale. If you would like some note, shoot an email over to the support email and tell them to CC Tommy.C
Post Reply