Skip to Content
avatar image
Former Member

Windows AD Configuration for Jboss with BI 4.2 SP3

We are currently using BI 4.2 SP3 version on Jboss EAS 6.4 web application server. So far we have been using Enterprise authentication and the system is working fine. We recently configured Jboss and BI for Windows AD (manual authentication). We can do manual authentication from CCM (as document from SAP Suggests) and client tools. However when we do this from BI Launchpad, it fails with the following 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. If you are not a member of the default domain, enter your user name as UserName@DNS_DomainName, and then try again. (FWM 00006)"

Tried many variations of user name DOMAIN/username, username@Domain etc. but of no use. Does any one know a way of finding out what's happening on Jboss and how to successfully login with windows AD from Launchpad?

I don't find any document from SAP Site regarding Jboss and windows AD configuration.

Environment: BI 4.2 SP3

OS : Windows 2012

Web application server: Jboss EAS 6.4


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 17, 2018 at 01:09 PM

    Any web/app server will need to access the java kerberos login module (typically bsclogin.conf) and configuration file (krb5.ini) in order to authenticate via AD/kerberos. We document the steps on setting this up with our prepackaged tomcat but 3rd party web/apps tend to change and some have to use their own configuration options so it's not as easy to keep up with that. By default using the same files as tomcat and specifying them via the jboss java options would be the 1st thing to try.


    Add comment
    10|10000 characters needed characters exceeded