Has anyone had success configuring AD Authentication with BO XIR2 and Tomcat? I am currently reading the Business Objects PDF “Configuring Active Directory Authentication using Java Application Server”, but I am skeptical that it will work. I am wondering if I am better off using IIS as my web server. Any ideas?
What is your rationale that IIS is any better than Tomcat? As far as I know, both implementations work. It simply boils down to your environment setup and of course your personal preference.
We have been using AD authentication with tomcat since the beginning of the summer. It works perfect. Just follow the instructions in the document you mentioned.
I have seen it(Ad w/Java App) work quite well actually. The setup is extremely sensitive and the slightest mistake in any of the steps may cause it to fail. You are best to follow the instructions you have and if you get to a specific error post it search BOB to review the numerous threads out there on the subject.
looking at the BOBJ document “Configuring Active Directory Authentication using Java Application Servers” I see that we are asked to download and run a SETSPN utility. I have spoken with network folks that will not run this until I can provide them with specifics regarding:
What this utility does.
What are the risks in running it.
I have noticed that there is a ton of information if I just Google SETSPN, but I don’t have much experience with Active Directory so I’m looking for a simpler explanation.
I’m not an expert on this, so someone feel free to chime in as necessary…
setspn is a utility to set a service principal name in active directory.
service principal names are associated with the security principal (user or groups) in whose security context the service executes. SPNs are used to support mutual authentication between a client application and a service. An SPN is assembled from information that a client knows about a service. Or, it can obtain information from a trusted third party, such as Active Directory. A service principal name is associated with an account and an account can have many service principal names.
So in this example the client application is tomcat and the service is the cms service. You would create a user called say, cms, and set a service principal name for that user only on the cms service, so that you can authenticate to active directory using tomcat which passes its authentication token to the cms service.
As long as the cms user has limited access(mine is just an ordinary domain user), and the SPN is only set for the cms user on the cms service, then the security risk is not too high. Another example of a SPN i needed to set is for the NT authentication of the sql server service since I changed it to a non-admin account and by default only admins are allowed to set automatically set SPN’s in active directory.