Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
LDAP with SSL.
 Login/Join
 
Platinum Member
posted
Hi,

I am trying to configure WebFOCUS for LDAP authentication over port 636(SSL connection). I am having issues with it when I looked at the trace i see that the client is trying to talk to
ldapURL=ldap://lpi1s511.ldapserver.com:636.

Is in't supposed to try to talk to
ldaps://lpi1s511.ldapserver.com:636 because it is a secure connection?.

Thanks.
 
Posts: 176 | Location: Desplaines | Registered: August 05, 2004Report This Post
<Jim Thorstad - WF Product Mgt.>
posted
While "ldaps://" is commonly used and supported by many LDAP providers it is not part of the RFC 2255 which defines the LDAP URL.

Your question doesn't state if you meant WebFOCUS "Managed Reporting" but I'll assume you did. The MR LDAP Wizard authentication driver in 52x and the MR Realm Driver in 53x both make secure and un-secure LDAP connections by issuing "ldap://" which explains your observation.

You would configure our MR drivers to make a secure connection, specify your port (636 in your case) and go.

All ldaps does for you is changes the meaning of the default port when not specified. For a complete explanation, see:

http://java.sun.com/products/jndi/tutorial/ldap/misc/url.html
 
Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders