Re: Syncope on AWS
at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1687) > ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1624) > ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) > ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483) > ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) > ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) > ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) > ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) > ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761) > ~[spring-beans-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867) > ~[spring-context-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543) > ~[spring-context-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:443) > ~[spring-web-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:325) > ~[spring-web-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:107) > ~[spring-web-4.3.9.RELEASE.jar:4.3.9.RELEASE] > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4853) > ~[catalina.jar:8.0.45] > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314) > ~[catalina.jar:8.0.45] > at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) > ~[catalina.jar:8.0.45] > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753) > ~[catalina.jar:8.0.45] > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729) > ~[catalina.jar:8.0.45] > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717) > ~[catalina.jar:8.0.45] > at > org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:976) > ~[catalina.jar:8.0.45] > at > org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1853) > ~[catalina.jar:8.0.45] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[?:1.8.0_141] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > ~[?:1.8.0_141] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [?:1.8.0_141] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [?:1.8.0_141] > at java.lang.Thread.run(Thread.java:748) [?:1.8.0_141] > 14:54:34.480 INFO org.apache.syncope.core.provisioning.java.ConnectorManager > - Done loading 0 connectors > 14:54:36.828 ERROR org.apache.syncope.core.logic.init.SAML2SPLoader - Could > not initialize the SAML 2.0 Service Provider certificate > java.io.IOException: Invalid keystore formatOn Aug 21, 2017, at 8:54 AM, > Francesco Chicchiriccò <ilgro...@apache.org> wrote: > > On 20/08/2017 14:43, John Stegeman wrote: >> Hello All, > > Hi John, > welcome to Apache Syncope :-) > >> We
Syncope on AWS
Hello All, We have installed Syncope into AWS’s CodePipline (commit/build/deploy) and are using AWS’s Elastic Beanstalk environment. We pretty much have the entire process documented and working, however we are running into an error with Console. Essentially, when trying to access the Users and Groups administration area, Console kicks you out and returns to the login screen. We have tracked down where the return code is being processed. Also, we have checked the API via swagger. We also tried with the distribution WAR’s using the built-in H2 database with the same result.. The rest of console seems to function properly. In the console.log this errore appears at the top of the log: 11:38:28.163 ERROR org.apache.cxf.jaxrs.utils.JAXRSUtils - No message body reader has been found for class org.apache.syncope.common.lib.to.ErrorTO, ContentType: text/html;charset=iso-8859-1 11:38:28.175 ERROR org.apache.cxf.jaxrs.utils.JAXRSUtils - No message body reader has been found for class java.util.List, ContentType: text/html;charset=iso-8859-1 11:38:28.177 ERROR org.apache.syncope.client.console.SyncopeConsoleRequestCycleListener - Exception found org.apache.wicket.WicketRuntimeException: Error attaching this container for rendering: [WebMarkupContainer [Component id = body]] And the subsequent REST call produces this error: at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) ~[tomcat-util.jar:8.0.45] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_141] Caused by: javax.xml.ws.WebServiceException: Remote exception with status code: NOT_FOUND at org.apache.syncope.client.lib.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:76) ~[syncope-client-lib-2.0.4.jar:2.0.4] at org.apache.syncope.client.lib.RestClientExceptionMapper.fromResponse(RestClientExceptionMapper.java:42) ~[syncope-client-lib-2.0.4.jar:2.0.4] Using swagger on GET/groups/own a 500 error is returned and GET/users returns a 404 error code. We have actually made great progress and will share with the community Any insight or suggestions is greatly appreciated. Thank you, John
