LDAP ISSUES - Discover Attributes

Jaymer

OK, I made a new BO: LDAPServer
Pointed to our server and clicked DISCOVER ATTRIBUTES

I only get these 14 fields.
Screen Shot 2017-03-13 at 4.04.21 PM.png
Is this what everyone else has?

From searching the forum, it looks like others have diff. fields in their log.

I made a Query to browse this data.
I noticed all the fields were 2000 bytes long.
If I add all the fields to the Query, it won't run. Will throw a PARSERERROR

A lot of trial and error eliminating fields and I finally get a browse where I can see whats up.
Since I can't display all the data in the query, I click on a row to bring up the form - this works only on some records - others throw PARSERERROR.

Garbage in this field may be the reason why.
Screen Shot 2017-03-13 at 4.07.55 PM.png
I reduced the size of the fields down to 200 for most, and 30 for the timestamps.
At least I can see the data its getting back now.

aware_support

A tip: make sure that you specify correct DN for BOTH the node that you want to see and it's parent node.

Jaymer

thx,
but I already went through the whole mess of figuring that out:

This is used in the BO for the DISCOVER ATTRIBUTES button:
OU=US,DC=acme,DC=com

it successfully connects and reads in the attributes. (shown in pic above)
I created a new BO named LDAPServer.
I'm not messing with the Login options yet - just trying to Query the LDAP object.

I get the following errors that change based on values in the PARENT NODE field:

if I have no PARENT NODE defined in the LDAP BO:
Exception thrown com.bas.connectionserver.server.D Internal error. No Such Object
com.bas.connectionserver.server.D: Internal error. No Such Object

if PARENT NODE = DC=acme,DC=com
Exception thrown com.bas.connectionserver.server.D Internal error. Referral
com.bas.connectionserver.server.D: Internal error. Referral
LDAPReferralException: Referral: ldap://com/DC=com

if PARENT NODE = OU=US,DC=acme,DC=com
Exception thrown com.bas.connectionserver.server.D Internal error. Sizelimit Exceeded
com.bas.connectionserver.server.D: Internal error. Sizelimit Exceeded

if PARENT NODE = OU=US
Exception thrown com.bas.connectionserver.server.D Internal error. Operations Error
com.bas.connectionserver.server.D: Internal error. Operations Error

CN=NC-CHARLOTTE,OU=DistributionList,OU=Accounts,OU=Akron,OU=Ohio,OU=US,DC=acme,DC=com
this worked, and returned 1 only row

What finally got it working was:
OU=Accounts,OU=Akron,OU=Ohio,OU=US,DC=acme,DC=com

Just now I was browsing through 761 LDAP records and the server has locked up - pegged CPU 100% for more than 5 mins.

Sorting on columns in a Query on LDAPServer doesn't work.
Filtering on the "distinguished Name" field, or "Object Category" field doesn't work.
Filtering on "name" field works.

Jaymer

OK, so I modified the Discover Attributes node field.
To me, it reads "enter any valid node on the LDAP server and I'll suck in all the fields"

But now I got a ton more fields that I did the first time.

It was: OU=US,DC=acme,DC=com
Changed to: DC=acme,DC=com
and I must have gotten 50 attributes.

But there's more, because at runtime, I get log errors:
Unable to set value of LDAP attribute sn into business object Phillips
Unable to set value of LDAP attribute msExchSafeSendersHash into business object ӏ�o
Unable to set value of LDAP attribute givenName into business object Bill
Unable to set value of LDAP attribute displayName into business object Phillips,Bill
Unable to set value of LDAP attribute sAMAccountName into business object bill.phillips
Unable to set value of LDAP attribute physicalDeliveryOfficeName into business object Akron
Unable to set value of LDAP attribute accountExpires into business object 92235807
Unable to set value of LDAP attribute cn into business object Phillips,Bill
Unable to set value of LDAP attribute pwdLastSet into business object 0
Unable to set value of LDAP attribute userAccountControl into business object 512
Unable to set value of LDAP attribute countryCode into business object 0
Unable to set value of LDAP attribute sAMAccountType into business object 4446368

these attributes are not in the list of ones DISCOVERED.
So its getting data from the server, and doesn't have a place in the Aware BO to put this data... but why not?
I have no idea what to put in there.
How do I see the LDAP tree structure from the OS? I may have to get the client's SysAdmin to see how he manages that server for better node names.

aware_support

You MUST know the exact structure of the LDAP server before you mess around with Aware IM. Otherwise, you are just shooting in the dark. There are some freeware tools that display the structure of LDAP or just ask the client for the tool he uses.

Jaymer

OK, I've successfully retrieved attributes and proceeded to Login Options.

I'm using sAMAccountName from LDAP. Added that to RegularUser and added that entry in Login Options.
I'm using the special direct login URL: /AwareIM/logonDirect.aw

I immediately get this error:
Screen Shot 2017-03-14 at 11.24.23 PM.png

I didn't think ActiveX was supported on Safari/Chrome, so I'm not sure what to do. This doesn't make a lot of sense if the requirement is to use IE (yuck!).
Suggestions please!

Jaymer

oh crap,
i see in the manual there is a NOTE about this:
Screen Shot 2017-03-15 at 12.11.18 AM.png