Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Access Manager Appliance installation Issues

On 12-01-2019 9:46 PM, squadri wrote:
>


> You nailed it perfectly my friend. Its horrifying to know that the
> checksum didnt match and I had not focussed on that one possibility.
> However, did a fresh download and proceeded with fresh deployment of
> appliance after verifying checksum this time :pp . It shows both the
> clusters(IDP and Access Gateway) created.
> Appreciate your wonderful supporting ideas.


Glad its fixed 🙂


> Now moving to the next step. Our main objective is to protect our web
> based application with NAM. To begin with, we need to implement this
> solution to Groupwise WebAccess and SSPR for our eDirectory Users. Can
> you suggest the best possible and easy approach to do so?
> Please note that this is our first deployment of NAM4.4.



As per Ben's (ScorpionSting) response, both GW WebAccess and SSPR are quite well documented on how to successfully protect them with NAM. I do recall
that one version of GW WebAccess had an issue with accepting the authz header for SSO. Its mentioned in this forum in an older thread. I don't recall
what GW version was affected though.


--
Cheers,
Edward
0 Likes
syed_17 Super Contributor.
Super Contributor.

Re: Access Manager Appliance installation Issues

edmaa;2493475 wrote:
On 12-01-2019 9:46 PM, squadri wrote:
>


> You nailed it perfectly my friend. Its horrifying to know that the
> checksum didnt match and I had not focussed on that one possibility.
> However, did a fresh download and proceeded with fresh deployment of
> appliance after verifying checksum this time :pp . It shows both the
> clusters(IDP and Access Gateway) created.
> Appreciate your wonderful supporting ideas.


Glad its fixed 🙂


> Now moving to the next step. Our main objective is to protect our web
> based application with NAM. To begin with, we need to implement this
> solution to Groupwise WebAccess and SSPR for our eDirectory Users. Can
> you suggest the best possible and easy approach to do so?
> Please note that this is our first deployment of NAM4.4.



As per Ben's (ScorpionSting) response, both GW WebAccess and SSPR are quite well documented on how to successfully protect them with NAM. I do recall
that one version of GW WebAccess had an issue with accepting the authz header for SSO. Its mentioned in this forum in an older thread. I don't recall
what GW version was affected though.


--
Cheers,
Edward


Thanks for your advice but I am confused with the start up to it. Can you suggest some useful idea to kick start working and testing NAM appliance. The sample application doesnt seem to behave as documented or probably I fail to understand it :pp . Are there some good video tutorials available for new bees to guide with NAM 4.4 implementation!!! Any helpful ideas will be highly appreciated.
0 Likes
syed_17 Super Contributor.
Super Contributor.

Re: Access Manager Appliance installation Issues

squadri;2494021 wrote:
Thanks for your advice but I am confused with the start up to it. Can you suggest some useful idea to kick start working and testing NAM appliance. The sample application doesnt seem to behave as documented or probably I fail to understand it :pp . Are there some good video tutorials available for new bees to guide with NAM 4.4 implementation!!! Any helpful ideas will be highly appreciated.


Found the reason for issues with sample application in release notes.. it says due to portal_roles policy disabled. For vidoe tutorials looked at the following : https://www.youtube.com/watch?v=Ru-ktLNy9ls
However, couldn't really got going with it in real.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Access Manager Appliance installation Issues

On 20-01-2019 5:46 PM, squadri wrote:
>


> Thanks for your advice but I am confused with the start up to it. Can
> you suggest some useful idea to kick start working and testing NAM
> appliance. The sample application doesnt seem to behave as documented or
> probably I fail to understand it :pp . Are there some good video
> tutorials available for new bees to guide with NAM 4.4 implementation!!!
> Any helpful ideas will be highly appreciated.
>
>


OK, so lets start with GroupWise WebAccess. I guess you currently already have users using it? If so, they would use something like
www.yourcompany.com/gw/webacc. One of the ways to 'move' users to NAM is to simply build a proxy for www.yourcompany.com and proxy all the requests
for /gw/webacc to your webaccess server.

Once that is all working you can start playing with authentication and authorization and single sign-on.

1) Authentication. When you enable authentication all users are required to identify themselves first before they are allowed access. You can do this
on a per resource basis and each resource can contain a set of URLs.
2) Authorization. This is where you can restrict access to groups of users based on attributes and/or roles a user has assigned.
3) Single Sign-on. When you enable authentication on the protected resources in NAM users have to identify. Now it could be that the backend app also
require authentication so in that case, a user would have to authenticate multiple times which would give for quite a poor user experience. So NAM has
ways to create a single sign-on experience to the app. These are:
a) Inject credentials in a header. Very often apps can be configured to use basic authentication which uses the authorization header. The creds are
concatenated and base64 encoded and then injection. Obviously with NAM you can inject any user info (as long as its available in your LDAP store so
NAM can read the info) in any http header. Its up to the app to read it and understand it.
b) formfill. Most apps (like webaccess) challenge users through a nice webpage. NAM can autofill these creds and then through some javascript smarts
make the browser auto submit the form so it appears as a single sign-on experience.

Hopefully this helps a little


--
Cheers,
Edward
0 Likes
syed_17 Super Contributor.
Super Contributor.

Re: Access Manager Appliance installation Issues

edmaa;2493369 wrote:
On 10-01-2019 6:44 PM, squadri wrote:
>
> edmaa;2493357 Wrote:
>> On 10-01-2019 7:46 AM, squadri wrote:
>>>
>>> Yes it�s a virtual machine with 8GB memory. It does not show errors

>> on
>>> installation. I noted seeing the messages �installing the access

>> Gateway
>>> � . But like you mentioned, will again reinstall with added memory

>> and
>>> check. How can I check if tomcat or other services/processes for

>> access
>>> Gateway are running or not?
>>>
>>>

>> 8 GB is more than sufficient. With 4GB the install works fine (obviously
>> not suited for production load tho). Can you check if you can see a file
>> called /tmp/novell_access_manager/configure_cluster_<date>.log and post
>> the output here? It should contain the output of the cluster creation
>> and if
>> there were any errors.
>>
>> --
>> Cheers,
>> Edward

>
> Hello Edward,
> As mentioned earlier, I once again installed NAM appliance ,this time
> with 12 GB RAM , the problem still appears to be the same. Here is the
> output of configure_cluster log copied from your mentioned path :
> -Creating clusters...
> Creating the Identity Server cluster...
> /opt/novell/java/bin/java -classpath
> "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*"
> com.volera.roma.app.handler.AutoConfigHandlerWrapper configureIdpCluster
> nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25
> cn=admin,o=novell XXXXX
> Invoking IDP cluster creation URL :
> https://192.168.1.25:8443/nps/rest/clusterconfig/idpcluster?ClusterName=IDPCluster&eDirReplicaIPAddress=192.168.1.25&dnsName=nam.almabani.com.sa&AdminName=cn=admin,o=novell&AdminPassword=xxxx
> Response: 200
>
> Creating the Access Gateway cluster...
> /opt/novell/java/bin/java -classpath
> "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*"
> com.volera.roma.app.handler.AutoConfigHandlerWrapper configureAGCluster
> nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25
> cn=admin,o=novell XXXXX ag-4A2FD1247EC91A6C
> Invoking Access Gateway cluster creation URL :
> https://192.168.1.25:8443/roma/autoconfig/cntl?handler=group_create&actionCmd=SaveNameAndDesc&groupCluster_check=on&groupName=AG-Cluster&groupPrimaryServer=ag-4A2FD1247EC91A6C&groupUrl=192.168.1.25&ag-4A2FD1247EC91A6C_checkbox_vcp=ag-4A2FD1247EC91A6C
> *Response code:302*
>
> Importing the default policies...
> /opt/novell/java/bin/java -classpath
> "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*"
> com.volera.roma.app.handler.AutoConfigHandlerWrapper configurePolicies
> nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25
> cn=admin,o=novell XXXXX
> Invoking URL:
> https://192.168.1.25:8443/roma/autoconfig/cntl?handler=group_create&actionCmd=ImportDefaultPolicies&policycollectionid=xpemlPEP&prevstep=savepolicy&containerid=mastercdn
> Response code:200
>
> Enabling role based policies for the Identity Server cluster...
> /opt/novell/java/bin/java -classpath
> "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*"
> com.volera.roma.app.handler.AutoConfigHandlerWrapper enableIDPRoles
> nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25
> cn=admin,o=novell XXXXX
> Invoking URL: http://tinyurl.com/y74q4wae
> Response code:200-
>
>
> Its noticed that Response code for creating Access Gateway cluster
> appears to be code:302 unlike others where it shows Response code:200 .
> Does that mean an error?? If yes, please guide how to fix it.
>
>

I'm also seeing a 302 response code here in my lab when it creates the AG cluster. Can you check if the ESP has actually started?

cat /opt/novell/nam/mag/logs/catalina.out



--
Cheers,
Edward


here is the catalina.out full output, ignore the earlier post above which is partly posted:

Jan 10, 2019 10:17:10 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'xmlValidation' to 'false' did not find a matching property.
Jan 10, 2019 10:17:10 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'xmlNamespaceAware' to 'false' did not find a matching property.
Jan 10, 2019 10:17:10 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib64:/opt/novell/eDirectory/lib64:/opt/novell/lib64
Jan 10, 2019 10:17:10 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-nio-127.0.0.1-9009"]
Jan 10, 2019 10:17:10 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
INFO: Using a shared selector for servlet write/read
Jan 10, 2019 10:17:10 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 746 ms
Jan 10, 2019 10:17:10 AM org.apache.catalina.users.MemoryUserDatabase open
SEVERE: The specified user database [conf/tomcat-users.xml] could not be found
Jan 10, 2019 10:17:10 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Jan 10, 2019 10:17:10 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat
Jan 10, 2019 10:17:10 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/novell/nam/mag/webapps/agm
Jan 10, 2019 10:17:10 AM org.apache.catalina.startup.SetContextPropertiesRule begin
WARNING: [SetContextPropertiesRule]{Context} Setting property 'debug' to '0' did not find a matching property.
Jan 10, 2019 10:17:12 AM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
AMLoggingInit.<static initializer block>, configuring log4j, configPath=/etc/opt/novell/amlogging/config/log4j.xml
log4j:WARN Continuable parsing error 41 and column 17
log4j:WARN The content of element type "appender" must match "(errorHandler?,param*,rollingPolicy?,triggeringPolicy?,connectionSource?,layout?,filter*,appender-ref*)".
Creating ActiveMQ Connection...
Creating ActiveMQ Connection...
Confirm Queue: queue://AMLoggingMonitor-local-confirm
Consuming queue: AMLoggingMonitor-local-indicate
indicateSession: ActiveMQSession {id=ID:nam.almabani.com.sa-49433-1547104632563-0:0:3,started=false}
respondSession: ActiveMQSession {id=ID:nam.almabani.com.sa-49433-1547104632563-0:0:4,started=false}
log4j:WARN No such property [host] in com.novell.nacm.logging.audit.AMSyslogAppender.
log4j:WARN No such property [port] in com.novell.nacm.logging.audit.AMSyslogAppender.
log4j:WARN No such property [protocol] in com.novell.nacm.logging.audit.AMSyslogAppender.
log4j:WARN No such property [cacheenabled] in com.novell.nacm.logging.audit.AMSyslogAppender.
log4j:WARN No such property [cachedir] in com.novell.nacm.logging.audit.AMSyslogAppender.
log4j:WARN No such property [cachemaxfilesize] in com.novell.nacm.logging.audit.AMSyslogAppender.
initiateStartup() called.
initiateStartup(), CONFIGURATION FILE /opt/novell/nam/mag/webapps/agm/WEB-INF/config/current/config.xml NOT FOUND!!! Using factory defaults.
initateStartup(), Setting management IP as 192.168.1.25
initateStartup(), Setting device ID as ag-4A2FD1247EC91A6C
Creating ActiveMQ Connection...
Creating ActiveMQ Connection...
Confirm Queue: queue://GatewayManager-local-confirm
Consuming queue: GatewayManager-local-indicate
indicateSession: ActiveMQSession {id=ID:nam.almabani.com.sa-49433-1547104632563-0:1:3,started=false}
respondSession: ActiveMQSession {id=ID:nam.almabani.com.sa-49433-1547104632563-0:1:4,started=false}
log4j:WARN Continuable parsing error 41 and column 17
log4j:WARN The content of element type "appender" must match "(errorHandler?,param*,rollingPolicy?,triggeringPolicy?,connectionSource?,layout?,filter*,appender-ref*)".
[]
Starting to add global filter settings
High Volume Events initializaed
final custom extension string
done with global filter settings
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: ag-maga, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: ag, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: ag-lag, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: ag-mag, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: ag-mag, tomcat restart command is: /bin/bash -c "/etc/init.d/novell-mag restart"
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: idp-idp, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: idp-idp, tomcat restart command is: /bin/bash -c "/etc/init.d/novell-idp restart"
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: idp-esp, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: agent-agent, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: jccserver, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: system, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: ar, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.client.JCCClientImpl <init>
INFO: Starting client 4A2FD1247EC91A6C of type ag
Jan 10, 2019 10:17:13 AM com.novell.jcc.client.JCCClientImpl$_B run
INFO: server connection thread started
Jan 10, 2019 10:17:13 AM com.novell.jcc.util.JCCSettings A
INFO: Current settings
rmiPort: 1197
localMgmtPort: 1443
localMgmtIP: 192.168.1.25
remoteMgmtPort: 8444
remoteMgmtIP: [192.168.1.25]
jccProxyPort: 2483
agProxyPort: 444
sslvpnProxyPort: 3423
healthFreq: 300
statsFreq: 300
remoteMgmtIPFreq: 3600
externTomcatDir: /opt/novell/nam/mag
secure: true

Jan 10, 2019 10:17:14 AM com.novell.jcc.client.JCCClientImpl$_B D
INFO: attempting to contact RMI server on 127.0.0.1:1197
Jan 10, 2019 10:17:15 AM com.novell.jcc.client.JCCClientImpl queueAlert
INFO: queuing alert: Severe: Failure in Audit, local syslog is offline. at Thu Jan 10 10:17:15 AST 2019 for ag-4A2FD1247EC91A6C
initiateStartup() completed
Jan 10, 2019 10:17:15 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/novell/nam/mag/webapps/agm has finished in 5,405 ms
Jan 10, 2019 10:17:15 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/novell/nam/mag/webapps/nesp
Jan 10, 2019 10:17:15 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Context/Manager} Setting property 'saveOnRestart' to 'false' did not find a matching property.
log4j:ERROR No appender named [AMAuditSyslogAuditAppender] could be found.
Jan 10, 2019 10:17:23 AM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Jan 10, 2019 10:17:24 AM com.sun.xml.ws.server.MonitorBase createRoot
INFO: Metro monitoring rootname successfully set to: com.sun.metro=/,type=WSEndpoint,name=/nesp-provider
Jan 10, 2019 10:17:25 AM com.sun.xml.ws.server.MonitorBase createRoot
INFO: Metro monitoring rootname successfully set to: com.sun.metro=/,type=WSEndpoint,name=/nesp-SecurityTokenService-STS_Port
Jan 10, 2019 10:17:25 AM com.sun.xml.ws.server.MonitorBase createRoot
INFO: Metro monitoring rootname successfully set to: com.sun.metro=/,type=WSEndpoint,name=/nesp-SecurityTokenService-STS_Port_saml
Jan 10, 2019 10:17:25 AM com.sun.xml.ws.server.MonitorBase createRoot
INFO: Metro monitoring rootname successfully set to: com.sun.metro=/,type=WSEndpoint,name=/nesp-SecurityTokenService-STS_Port_active12
Jan 10, 2019 10:17:25 AM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing
Jan 10, 2019 10:17:25 AM org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer addServletWithApplication
SEVERE: Mapping conflict. A Servlet registration exists with same mapping as the Jersey servlet application, named net.microfocus.impersonation.service.v1.application.ImpersonationApplication, at the servlet mapping, /impersonation/*. The Jersey servlet is not deployed.
Jan 10, 2019 10:17:25 AM org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer addServletWithApplication
INFO: Registering the Jersey servlet application, named net.microfocus.mobileaccess.service.v1.application.MobileAccessApplication, at the servlet mapping /mobileaccess/*, with the Application class of the same name.
Jan 10, 2019 10:17:25 AM org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer addServletWithApplication
INFO: Registering the Jersey servlet application, named net.microfocus.basicsso.service.v1.application.BasicSSOApplication, at the servlet mapping /basicsso/*, with the Application class of the same name.
Jan 10, 2019 10:17:25 AM org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer addServletWithApplication
INFO: Registering the Jersey servlet application, named com.novell.nam.nidp.risk.RiskRESTApplication, at the servlet mapping /risk/*, with the Application class of the same name.
Jan 10, 2019 10:17:25 AM org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer addServletWithApplication
INFO: Registering the Jersey servlet application, named com.novell.nidp.rest.NIDSRestApplication, at the servlet mapping /rest/*, with the Application class of the same name.
A critical error has occurred during startup. {0}Evaluation code has been disabled as of Fri, Nov 30, 2018.
Jan 10, 2019 10:17:25 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
Jan 10, 2019 10:17:25 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
Filter initialized! 'SameOriginFilter'
Filter initialized! 'ClusterRequestFilter'
Jan 10, 2019 10:17:26 AM org.glassfish.jersey.server.ApplicationHandler initialize
INFO: Initiating Jersey application, version Jersey: 2.10.1 2014-06-30 13:53:32...
Jan 10, 2019 10:17:26 AM com.novell.nam.nidp.oauth.core.TokenServiceImpl <init>
INFO: TokenServiceImpl created
Jan 10, 2019 10:17:26 AM org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter OAuthApplicationJspMvcFilter
MultiException stack 1 of 3
java.lang.NullPointerException
at com.novell.nam.nidp.oauth.nidp.NIDPClientConfig.init(NIDPClientConfig.java:41)
at com.novell.nam.nidp.oauth.nidp.NIDPClientConfig.<init>(NIDPClientConfig.java:37)
at com.novell.nam.nidp.oauth.nidp.wrapper.NIDPConfigServiceWrapper.<init>(NIDPConfigServiceWrapper.java:36)
at com.novell.nam.nidp.oauth.nidp.config.NIDPOAuth2ConfigServiceFactory.provide(NIDPOAuth2ConfigServiceFactory.java:34)
at com.novell.nam.nidp.oauth.nidp.config.NIDPOAuth2ConfigServiceFactory.provide(NIDPOAuth2ConfigServiceFactory.java:15)
at org.jvnet.hk2.internal.FactoryCreator.create(FactoryCreator.java:96)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456)
at org.jvnet.hk2.internal.PerLookupContext.findOrCreate(PerLookupContext.java:69)
at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2151)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98)
at org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:618)
at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:77)
at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:214)
at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:237)
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:360)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456)
at org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:114)
at org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:102)
at org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:97)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture.run(Cache.java:154)
at org.glassfish.hk2.utilities.cache.Cache.compute(Cache.java:199)
at org.jvnet.hk2.internal.SingletonContext.findOrCreate(SingletonContext.java:153)
at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2151)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:87)
at org.glassfish.jersey.internal.inject.Providers.getAllRankedProviders(Providers.java:235)
at org.glassfish.jersey.server.ApplicationHandler.getProcessingProviders(ApplicationHandler.java:672)
at org.glassfish.jersey.server.ApplicationHandler.initialize(ApplicationHandler.java:448)
at org.glassfish.jersey.server.ApplicationHandler.access$500(ApplicationHandler.java:163)
at org.glassfish.jersey.server.ApplicationHandler$3.run(ApplicationHandler.java:323)
at org.glassfish.jersey.internal.Errors$2.call(Errors.java:289)
at org.glassfish.jersey.internal.Errors$2.call(Errors.java:286)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.processWithException(Errors.java:286)
at org.glassfish.jersey.server.ApplicationHandler.<init>(ApplicationHandler.java:320)
at org.glassfish.jersey.server.ApplicationHandler.<init>(ApplicationHandler.java:285)
at org.glassfish.jersey.servlet.WebComponent.<init>(WebComponent.java:310)
at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:170)
at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:388)
at org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:279)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:260)
at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:105)
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4700)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5340)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1129)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1871)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
MultiException stack 2 of 3
java.lang.IllegalArgumentException: While attempting to resolve the dependencies of com.novell.nam.nidp.oauth.core.filters.OAuth2ProxyFilter errors were found
at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:249)
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:360)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456)
at org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:114)
at org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:102)
at org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:97)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture.run(Cache.java:154)
at org.glassfish.hk2.utilities.cache.Cache.compute(Cache.java:199)
at org.jvnet.hk2.internal.SingletonContext.findOrCreate(SingletonContext.java:153)
at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2151)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:87)
at org.glassfish.jersey.internal.inject.Providers.getAllRankedProviders(Providers.java:235)
at org.glassfish.jersey.server.ApplicationHandler.getProcessingProviders(ApplicationHandler.java:672)
at org.glassfish.jersey.server.ApplicationHandler.initialize(ApplicationHandler.java:448)
at org.glassfish.jersey.server.ApplicationHandler.access$500(ApplicationHandler.java:163)
at org.glassfish.jersey.server.ApplicationHandler$3.run(ApplicationHandler.java:323)
at org.glassfish.jersey.internal.Errors$2.call(Errors.java:289)
at org.glassfish.jersey.internal.Errors$2.call(Errors.java:286)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.processWithException(Errors.java:286)
at org.glassfish.jersey.server.ApplicationHandler.<init>(ApplicationHandler.java:320)
at org.glassfish.jersey.server.ApplicationHandler.<init>(ApplicationHandler.java:285)
at org.glassfish.jersey.servlet.WebComponent.<init>(WebComponent.java:310)
at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:170)
at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:388)
at org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:279)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:260)
at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:105)
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4700)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5340)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1129)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1871)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
MultiException stack 3 of 3
java.lang.IllegalStateException: Unable to perform operation: resolve on com.novell.nam.nidp.oauth.core.filters.OAuth2ProxyFilter
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:389)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456)
at org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:114)
at org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:102)
at org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:97)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture.run(Cache.java:154)
at org.glassfish.hk2.utilities.cache.Cache.compute(Cache.java:199)
at org.jvnet.hk2.internal.SingletonContext.findOrCreate(SingletonContext.java:153)
at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2151)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:87)
at org.glassfish.jersey.internal.inject.Providers.getAllRankedProviders(Providers.java:235)
at org.glassfish.jersey.server.ApplicationHandler.getProcessingProviders(ApplicationHandler.java:672)
at org.glassfish.jersey.server.ApplicationHandler.initialize(ApplicationHandler.java:448)
at org.glassfish.jersey.server.ApplicationHandler.access$500(ApplicationHandler.java:163)
at org.glassfish.jersey.server.ApplicationHandler$3.run(ApplicationHandler.java:323)
at org.glassfish.jersey.internal.Errors$2.call(Errors.java:289)
at org.glassfish.jersey.internal.Errors$2.call(Errors.java:286)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.processWithException(Errors.java:286)
at org.glassfish.jersey.server.ApplicationHandler.<init>(ApplicationHandler.java:320)
at org.glassfish.jersey.server.ApplicationHandler.<init>(ApplicationHandler.java:285)
at org.glassfish.jersey.servlet.WebComponent.<init>(WebComponent.java:310)
at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:170)
at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:388)
at org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:279)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:260)
at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:105)
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4700)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5340)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1129)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1871)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Filter initialized! 'SessionAssuranceFilter'
Filter initialized! 'XSSDetectionFilter'
Filter initialized! 'WSInterfaceFilter'
Filter initialized! 'nidpJspFilter'
Jan 10, 2019 10:17:26 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: One or more Filters failed to start. Full details will be found in the appropriate container log file
Jan 10, 2019 10:17:26 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/nesp] startup failed due to previous errors
Jan 10, 2019 10:17:26 AM com.sun.xml.ws.transport.http.servlet.WSServletDelegate destroy
INFO: WSSERVLET15: JAX-WS servlet destroyed
Jan 10, 2019 10:17:26 AM com.sun.xml.ws.server.WSEndpointImpl closeManagedObjectManager
INFO: Closing Metro monitoring root: com.sun.metro=/,type=WSEndpoint,name=/nesp-provider
Jan 10, 2019 10:17:26 AM com.sun.xml.ws.server.WSEndpointImpl closeManagedObjectManager
INFO: Closing Metro monitoring root: com.sun.metro=/,type=WSEndpoint,name=/nesp-SecurityTokenService-STS_Port
Jan 10, 2019 10:17:26 AM com.sun.xml.ws.server.WSEndpointImpl closeManagedObjectManager
INFO: Closing Metro monitoring root: com.sun.metro=/,type=WSEndpoint,name=/nesp-SecurityTokenService-STS_Port_saml
Jan 10, 2019 10:17:26 AM com.sun.xml.ws.server.WSEndpointImpl closeManagedObjectManager
INFO: Closing Metro monitoring root: com.sun.metro=/,type=WSEndpoint,name=/nesp-SecurityTokenService-STS_Port_active12
Jan 10, 2019 10:17:26 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextDestroyed
INFO: WSSERVLET13: JAX-WS context listener destroyed
Jan 10, 2019 10:17:27 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextDestroyed
INFO: WSSERVLET13: JAX-WS context listener destroyed
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.