000021469 - Global catalog authentication to ClearTrust protected resource

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000021469
Applies ToRSA ClearTrust 5.5.2
Microsoft Windows 2000 SP4
Active Directory Global Catalog
IssueGlobal catalog authentication to ClearTrust protected resource

When utilizing Global Catalog, the Aserver debug log shows the following:

13:15:42:620 [*] [MUXWORKER-3] - AuthorizationAPI.authenticate( {CLIENT_VERSION=5, SC_TOUCH_TIME=1096056942000, SC_CREATION_TIME=1096056942000, AUTHENTICATION_TYPE=SC_BASIC, SC_END_USER_IP=10.7.193.41, SC_USER_ID=jwai, SC_GET_TOKEN_CONTENTS=true, CREDENTIALS=*****, SC_SECURID_STATUS=127}, {CLIENT_IP=10.7.193.41, CLIENT_PORT=35098, BROWSER_IP=10.7.193.41, USER_GROUPS_ENABLED=false, USER_PROPERTIES_ENABLED=false, TOKENS_ENABLED=true} ) returning {EXCEPTION_MESSAGE=00000000: LdapErr: DSID-0C0905FF, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece


Aserver log shows the following:

sequence_number=12,2004-09-24 15:40:57:64 PDT,messageID=9,user=jwai,client_ip_address=10.10.33.102,client_port=35351,browser_ip_address=10.7.193.41,result_code=101,result_action=Data Store Error
Web browser displays the following:

Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead.

The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
CauseSuccessful bind has not been established to the Global Catalog for authentication purposes
ResolutionTo correct this issue, ensure you have completed the configuration as specified within the RSA ClearTrust 5.5 Installation and Configuration guide on page 62. Ensure that you have values specified for:

cleartrust.data.ldap.directory.gc.hostname :
cleartrust.data.ldap.directory.gc.port :
cleartrust.data.ldap.directory.gc.binddn   :
cleartrust.data.ldap.directory.gc.password :
cleartrust.data.ldap.directory.gc-bind.hostname :
cleartrust.data.ldap.directory.gc-bind.port :
cleartrust.data.ldap.directory.gc-bind.binddn   :
cleartrust.data.ldap.directory.gc-bind.password :

where "gc" is the label for my global catalog.

Also ensure you have configured the correct value for your cleartrust.data.ldap.auxuser.dnattribute.
WorkaroundConfigured ClearTrust to use Global Catalog bind
Legacy Article IDa23190

Attachments

    Outcomes