Anonymous_User Absent Member.
Absent Member.
260 views

Unable to configure SSO with NetIQ Reporting Module


I was trying to configure SSO with reporting module. After inspecting
the reporting module login page with the web developer plugin for
mozilla, I found that there is no form name, only the form-id is
present. I used the same in the form matching criteria. However whenever
i get past the ldap authentication I am getting the reporting module
login page but cant login to the reporting module. I get the error in
the reporting module log:

ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/IDMRPT].[AuthServlet]]
(http-0.0.0.0-8280-11) Servlet.service() for servlet A
uthServlet threw exception
org.apache.http.conn.HttpHostConnectException: Connection to
http://reporting.vistrit.lab:8280 refused
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:127)
at
org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:147)
at
org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:108)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554)
at
org.spiffyui.server.AuthServlet.doLogin(AuthServlet.java:275)
at
org.spiffyui.server.AuthServlet.service(AuthServlet.java:155)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
at java.net.Socket.connect(Socket.java:579)
at
org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123)
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:123)


--
joydeepg
------------------------------------------------------------------------
joydeepg's Profile: https://forums.netiq.com/member.php?userid=7638
View this thread: https://forums.netiq.com/showthread.php?t=52268

0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Unable to configure SSO with NetIQ Reporting Module

On 11/21/2014 08:54 AM, joydeepg wrote:
> org.apache.http.conn.HttpHostConnectException: Connection to
> http://reporting.vistrit.lab:8280 refused


This seems pretty clear: the system that was found (presumably by NAM) at
reporting.vistrit.lab actively refused the connection to TCP 8280. I
would guess that either the port or the address as resolved on the NAM box
is wrong. Does the NAM box have access to resolve this address like other
more-internal systems may?

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Unable to configure SSO with NetIQ Reporting Module


The configuration in the NAM box is domain based. I have selected Host
Header as Forward Recieved Host Name. The SSO with the userapp is
working fine and it resolves to userapp.vistrit.lab:8180. The reporting
module is installed in the same linux box as that of the user
application and is running on port 8280.


--
joydeepg
------------------------------------------------------------------------
joydeepg's Profile: https://forums.netiq.com/member.php?userid=7638
View this thread: https://forums.netiq.com/showthread.php?t=52268

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Unable to configure SSO with NetIQ Reporting Module

On 11/23/2014 12:24 AM, joydeepg wrote:
>
> The configuration in the NAM box is domain based. I have selected Host
> Header as Forward Recieved Host Name. The SSO with the userapp is
> working fine and it resolves to userapp.vistrit.lab:8180. The reporting
> module is installed in the same linux box as that of the user
> application and is running on port 8280.


If you believe everything is set correctly, then get a LAN trace and find
out what NAM is doing to get a connection refused when accessing something
on TCP 8280; when you find what that something is (the right box, the
wrong box, or something more odd) then perhaps it will help you find the
cause. For now, the error is clear: whatever is accessed is actively
refusing connections to TCP 8280.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Unable to configure SSO with NetIQ Reporting Module


The problem was with the Host Header, it will be Web Server Host Name
instead of the Forward Received Host Name. There I mentioned the
hostname of the linux box containing the reporting module and now I am
able to login to the reporting module


--
joydeepg
------------------------------------------------------------------------
joydeepg's Profile: https://forums.netiq.com/member.php?userid=7638
View this thread: https://forums.netiq.com/showthread.php?t=52268

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.