Screendesk

Login Get Screendesk for Free

Internal Audit: Bindings collection does not contain an item with ID

The speaker explains how to create a new binding in an MS Teams configuration and explains how to sync a record with the application. They demonstrate how to change the phone number and save the new configuration, and explain how to restart the application and the robot. They also mention that a change to the user in the directory will require a restart of the application and a change to the user in the application.

K

Karl Newstead created this recording · almost 2 years ago

Developer Tools

Developer Tool Settings

Wrap text

Auto-scroll with playback

Developer Tools FAQ

This session does not contain any console logs.

Replays are enabled though, so feel free to close this tab
and try again after there has been some action on your page.

This session does not contain any network requests.

Replays are enabled though, so feel free to close this tab
and try again after there has been some action on your page.

No details

This video was uploaded. No details are available.

00:04

When you create a new binding

00:09

in an LDAP configuration.

00:11

It gets created

00:12

with, uh, a new unique identifier

00:19

here under the TNG LDAP binding tag.

00:26

Now every time

00:28

you create 1,

00:29

a new ID is used.

00:42

So you see that's now a different, uh, a different GUID.

00:47

And if we look at the GUID used in my test system here, which starts 4b7

00:54

and carries on like that, what we'll find

00:59

is that in a record that's synchronized

01:01

to LDAP,

01:03

that value

01:04

appears at the beginning of the unique ID.

01:08

And this means that if you do a sync either through the desktop UI or through the robot,

01:14

uh, the application can find the record

01:18

in the directory.

01:20

So just to demonstrate that here, I've got, uh, my user has a phone number.

01:26

And if I go to their record in the directory,

01:29

change the phone number, and apply,

01:32

then come back to the client

01:36

and sync.

01:40

We see the phone number changes.

01:43

So if you end up in a situation where the GUID is different in the binding,

01:49

for example, if you copy the database to a different environment

01:53

or if you edit the LDAP config and delete the original binding,

01:58

then a sync will fail.

02:00

So in my example,

02:02

I now have an LDAP config,

02:05

uh, with a new GUID for the binding that I'm using.

02:09

And

02:10

on my client, we can see

02:12

I've still got the original

02:14

GUID here in the record unique ID.

02:18

And if I try to sync,

02:22

I get the error

02:24

because

02:25

the collection of bindings doesn't contain

02:28

the, uh, the guid for the record

02:31

is expecting.

02:35

And it's the same if I try to run the sync held app job through app manager.

02:43

We see the error message here.

02:48

So to resolve this then,

02:53

open up notepad. Open the

02:56

LDAP config file.

03:10

And replace

03:13

the grid with the one that the system is expecting you to use.

03:19

And then save.

03:22

This will require a restart of the application pools,

03:30

And then, obviously, you'll need to restart the robot as well.

03:36

And then we'll just make a change to the

03:41

user again in the directory, go back to the application,

03:45

and we should find that the sync works without error.

Details

Date

07 Aug 2024, 14:48

Created by

K

Karl Newstead

Source

Upload

Assigned to

No assignees