Jespa SSO with NTLM in active directory

Question

Hai I have implemented Jespa SSO with ntlm authentication in Active directory with one Domain its work fine when we run the jespa app in the same system logged as the active directory user.But when we access the same app from the other system in same user of the domain the SSO doesn't work fine.The SSO doesn't starts the authorisation when we access it from the outer system with same network and the same domain.

My web.xml

    <?xml version="1.0" encoding="ISO-8859-1"?>
<web-app 
    xmlns="http://java.sun.com/xml/ns/j2ee" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" 
    version="2.4"> 

    <display-name>Jespa Examples</display-name>

    <filter>
        <filter-name>HttpSecurityFilter</filter-name>
        <filter-class>jespa.http.HttpSecurityFilter</filter-class>
        <init-param>
<!--
The properties.path parameter instructs the HttpSecurityService to load
properties from the named file. This file will be automatically reloaded
within 5 seconds after being modified without restarting the application
server. See The Jespa Operator's Manual for details.
-->
            <param-name>properties.path</param-name>
            <param-value>/WEB-INF/example_ntlm.prp</param-value>
        </init-param>
    </filter>

    <filter-mapping>
        <filter-name>HttpSecurityFilter</filter-name>
        <url-pattern>/*</url-pattern>
    </filter-mapping>

</web-app>

And my property file contains the following code

# To use this example edit the properties.path init-param in the web.xml
#
# This example HttpSecurityService properties file uses the
# NtlmSecurityProvider to authenticate and authorize clients with an Active
# Directory authority.
#
# Note: This is the equivalent of example_ntlm_web.xml but loaded
# indirectly with the HttpSecurityService properties.path property in
# the web.xml.

provider.classname = jespa.ntlm.NtlmSecurityProvider
http.parameter.username.name = username
http.parameter.password.name = password
http.parameter.logout.name = logout
#http.parameter.anonymous.name = anon
fallback.location = /jespa/Login.jsp
excludes = /Login.jsp
#groups.allowed = BUSICORP\\Domain Admins


#
# NtlmSecurityProvider properties
#
jespa.log.path = C:/Users/spartan/Desktop/jespa.log
jespa.log.level = 4
jespa.account.canonicalForm = 3

# Replace the following with properties determined in Step 1 of Installation

jespa.bindstr = HealthSystem.local
jespa.dns.servers = 127.0.0.1
#jespa.dns.site = Default-First-Site-name
jespa.service.acctname = hari$@HealthSystem.local
jespa.service.password = Spartan@1234

Anyone help me out to figure out the mischellaneous behaviour of jespa in my webapp

Jespa SSO with NTLM in active directory

0 Answers0