Hello,
I am having a problem with getting windows AD authentication working when I use Kerberos authentication. It works fine when I use NTLM authentication, but I heard the kerberos authentication (java) made for a simpler login (single sign on?), so I’ve been trying to get this to work. Whenever I check to ‘use kerberos authentication’ though, it gives the error:
"Account Information Not Recognized: Active Directory Authentication failed to log you on. Please contact your system administrator to make sure you are a member of a valid mapped group and try again. "
I have done everything in the pdfs on business objects website, have created a mapped group for crystal reports, made an account and did setspn.exe as instructed, created krb5.ini and bcsLogin.conf, and added the following to the tomcat java config:
-Djava.security.auth.login.config=C:\windows\bscLogin.conf
-Djava.security.krb5.conf=C:\windows\Krb5.ini
I wasn’t sure exactly what went in those 2 files, but here they are:
krb5.ini:
[libdefaults]
I had a problem like this here. Altough I could import groups and users via CMC, and despite being able to see klist success message, users could’nt still log on to Infoview.
After each logon attempt, a new error line like this was added to stdout.log:
“ERROR com.crystaldecisions.sdk.plugin.authentication.ldap.internal.SecWinADAuthentication - Cannot create LoginContext. Configuration error: Can not specify multiple entries for com.businessobjects.security.jgss.initiate”
From Tomcat, Java Infoview I get this error in stdout.log:
575554 [http-8080-Processor25] ERROR com.crystaldecisions.sdk.plugin.authentication.ldap.internal.SecWinADAuthentication - Cannot create LoginContext. No LoginModules configured for com.businessobjects.security.jgss.initiate
I need to know some places to look to change something.
Over a year and half ago I successfully had Infoview Tomcat authenticating to active directory but abandoned this due to the fully qualified login name as we have multiple AD domains. Enterprise authentication has been adequate for now. Now I am revisiting AD authentication. I have since upgraded with SP2, SP3 & FP3.4. So I don’t know if my problem is any of the patches, Java or what. I can test with kinit fine. I have a good krb5.ini and bsclogin.conf. I can login with AD from CMC. I can login with AD from Infoview .NET. My problem is just Tomcat Java Infoview.
There are over a dozen helpful threads I have studied and tried most of the suggestions. I don’t see any with the reference to the words “No LoginModules” which is a keyword to my problem.
Did you create the bscLogin.conf file? Also make sure you have this flag in your tomcat java options:
-Djava.security.auth.login.config=C:\WINNT\bscLogin.conf
Thanks for the hint, I did have a problem with my Krb5.ini and bscLogin.conf and I am closer to login. Now my error is:
185252 [http-8080-Processor24] ERROR com.crystaldecisions.sdk.plugin.authentication.ldap.internal.SecWinADAction - LoginContext failed. No valid credentials provided (Mechanism level: Fail to create credential. (63) - No service creds)
I have added many versions into setspn.exe hoping it’s the syntax to my server. Has anyone had the “No service creds” message and have any hints on where to search next for any changes?
I was having a similar problem. AD users could log in to the CMC, but not InfoView. When trying to log in to InfoView I would get the following error:
I also noticed the following error in the stdout.log
Similar to jcolares suggestion, I removed the line that points to the custom bscLogin.conf file in the Tomcat Java options and that seemd to work.
I tried just a blank bscLogin.conf file but that didn’t work for me.
I figured out why I was getting the following error in the stdout.log:
"ERROR com.crystaldecisions.sdk.plugin.authentication.ldap.internal.SecWinADAuthentication - Cannot create LoginContext. Configuration error: Can not specify multiple entries for com.businessobjects.security.jgss.initiate"
One of the steps in the configuration guide has you reference the bcsLogin.conf file either in the Java Options tab of Tomcat OR the java.security file, but not both.
I did both and that was why I got this error. I removed the line added in the java.security file and left the line in the Java Options tab and everything works fine now.