show user group list - Shows custom group only

[MP18]

Under group mappings of LDAP i have so many AD groups.

But when i run below command 

show user group list

Total: 1
1* : Custom Group

IT does not show me any group names from AD?

what is the reason for that?

Also what is difference between Custom group and AD groups in LDAP?

[Mick_Ball]

do you have the correct setting in device/user identification/group mapping settings/server profile/group objects/object class

this needs to set to group. if set to user it will not show in cli

AD groups are all users with the group attribute of "member"

custom groups are defined from an attribute of your choice, in affect...   a custom group...

[MP18]

I have same settings as you have shown

[Mick_Ball]

and are your groups listed in "included groups" as below

[MP18]

yes i have as you mentioned.

[Mick_Ball]

try...

show user group-mapping state all

can you see a line with "proxy state"

if you can then go to user-id agents and remove "use as ldap proxy"

[MP18]

no i do not see line with proxy state

[Mick_Ball]

are you running multi VSYS?

[MP18]

Not running multivsys

[Mick_Ball]

show user group-mapping statistics

how many groups are numbered here?

do you use policies based on group mappings and do they work?

[Mick_Ball]

also can you post a screen shot of the group include section.

[MP18]

show user group-mapping statistics

Name Vsys Groups Last-Action(secs) Next-Action(secs)
---------------------------------------------------------------------------
Group_Mapping_1 vsys1 11 2587 secs ago(took 0 secs) In 1013 secs
Group_Mapping_2 vsys1 8 2590 secs ago(took 0 secs) In 1010 secs

yes i use group mapping in policies and  they work

[MP18]

Added

[Mick_Ball]

in your screen shot i cannot see the OU for any of the groups.

could you find one of the groups in the available list and make sure it has no special characters in the OU.  as below.

if my OU was called developer&objects it would not show in CLI.

 

[Mick_Ball]

and i may have mentioned this before but just check your user ID agent settings and make sure none of them have a tick in "use as LDAP proxy".