I did a search on this subject, and though some issues were somewhat similar to be honest I still wasn't sure what the solution was (if any was mentioned) or where to start.
Users can access WebI through an LDAP server, but when I install BO 6.5.1 Client only on their machine, they type their same usernames and password but get the following error :
“USR 00105 - External Security Connector Error”
Why is this happening ? The users log in at the start of their day to a portal that leads them to many applications (financial system, CRM applications etc), and one of them is WebI. So their BO username/password authentication is 'bypassed' using the LDAP server when they normally log in to the portal at the beginning. Yet when I install the client locally on their machines, and try to run BO for them (using their username/password) I get the error message above.
How do I go about solving this problem ? please include as much detail as I'm a novice when it comes to servers/networking/connectivity etc. If you need any information from myself please do ask, here's some information that may be of help :
BusinessObjects Version : 6.5.1
Webserver : Apache
Application Server : Tomcat
Login Method for users into BO (using the generic portal for all applications) : LDAP
[quote:f63b3a9d10=“jayashree.r”]hi,
I did install LDAP security connector but i am still getting the same error. Can anyone help me in this regard please :(External SEcurity Connector error (USR 00105)
Jayashree
[/quote]
That is happening here as well.
For most users, the problem is in the LDAP system: Active Directory giving “wrong-case” usernames to BO, who only recognizes the “right case” users.
Correcting the LDAP environment (AD because 651 doesn’t directly “talk” to novell e-directories) which SHOULD give all ldap-authenticated users in sAMAccountName as upper-case. (any deviation from that should be “BO Technical accounts” who aren’t recognized by LDAP but who ARE defined in BO)
In our case, LDAP just gives authentication, all users are “internal in BO” as well, for authorisation.
That is happening here as well.
For most users, the problem is in the LDAP system …
In our case, LDAP just gives authentication, all users are “internal in BO” as well, for authorisation.
[/quote]
But at least one user can systematically connect to BO launching the full client, then opening documents (.rep) she receives from others (saved to local or shared disk)
When she opens the same document by double-clicking though, she gets the “security connection error”
Weird.
(BOB member since 2005-06-06)
(BOB member since 2007-06-18)
(BOB member since 2007-06-18)