Re: Syncope on AWS

2017-08-22 Thread Francesco Chicchiriccò

Hi John,
from the logs below I see something strange, e.g. that

org.apache.syncope.client.console.rest.UserRestClient.searchCount(UserRestClient.java:63)

throws NOT_FOUND, e.g. 404 - which barely means that the REST endpoint

/rest/users

returns 404.

I cannot figure out how this might happen. Maybe it is related to the 
troublesome setup you went through.


FYI, I am going to fix soon the 500 returned by /rest/groups/own when 
accessing via admin (which is not a regular user, so cannot be part of 
any group, actually).


Regards.

On 21/08/2017 18:21, John Stegeman wrote:

Hi Francesco,
I was authenticating into console and swagger using admin.

Also, I forget to add the environment details from initial email (my 
apologies):  Tomcat 8, Java 8, Amazon Linux 2017.03, current Syncope 
version



Just FYI:  During our setup, we have been bouncing back and forth 
between the AWS Elastic Beanstalk (EBS) environment using a mySQL 
backend and the Syncope Distribution environment.  Many of the errors 
have been resolved, partly due to us mapping the EBS environment 
environment variables and properly size the EBS env.


Per your instructions,

1.  We cleaned out the logs, logged into console with admin, 
navigated to Realms.  I then exited and pulled the logs from EBS.


2.  The log information was captured (below).

3.  I then attempted to access the Users tab within Realms and was 
punted back to the login screen (this the primary issue we are 
observing).


4.  We have learned a a lot over the last week about setting up 
Syncope, but may be missing something.  Any assistance is greatly 
appreciated.



In core-connie.log, all messages were INFO and it appears all the 
connector bundles were loaded.

In core-persistence.log no issues (found data and left untouched)
In core-rest.log it appears the WebApplicationContext initialized 
properly (with completed message).  No errors.



Below is the full content of console.log

14:31:09.478 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
14:31:09.486 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
14:31:09.495 ERROR 
org.apache.syncope.client.console.SyncopeConsoleRequestCycleListener 
- Exception found
org.apache.wicket.WicketRuntimeException: Error attaching this 
container for rendering: [WebMarkupContainer [Component id = body]]
at 
org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1837) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.onBeforeRender(Component.java:3916) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.internalBeforeRender(Component.java:950) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.beforeRender(Component.java:1018) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1825) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.onBeforeRender(Component.java:3916) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.internalBeforeRender(Component.java:950) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.beforeRender(Component.java:1018) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1825) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.onBeforeRender(Component.java:3916) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.internalBeforeRender(Component.java:950) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.beforeRender(Component.java:1018) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1825) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.onBeforeRender(Component.java:3916) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.markup.html.form.Form.onBeforeRender(Form.java:1807) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.internalBeforeRender(Component.java:950) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.beforeRender(Component.java:1018) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1825) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.onBeforeRender(Component.java:3916) 
~[wicket-core-7.7.0.jar:7.7.0]
at 
org.apache.wicket.Component.internalBeforeRender(Component.java:950) 

Re: Syncope on AWS

2017-08-21 Thread John Stegeman
> Hi Francesco,
> I was authenticating into console and swagger using admin.
> 
> Also, I forget to add the environment details from initial email (my 
> apologies):  Tomcat 8, Java 8, Amazon Linux 2017.03, current Syncope version
> 
> 
> Just FYI:  During our setup, we have been bouncing back and forth between the 
> AWS Elastic Beanstalk (EBS) environment using a mySQL backend and the Syncope 
> Distribution environment.  Many of the errors have been resolved, partly due 
> to us mapping the EBS environment environment variables and properly size the 
> EBS env.   
> 
> Per your instructions, 
> 
> 1.  We cleaned out the logs, logged into console with admin, navigated to 
> Realms.  I then exited and pulled the logs from EBS.
> 
> 2.  The log information was captured (below).
> 
> 3.  I then attempted to access the Users tab within Realms and was punted 
> back to the login screen (this the primary issue we are observing).
> 
> 4.  We have learned a a lot over the last week about setting up Syncope, but 
> may be missing something.  Any assistance is greatly appreciated.
> 
> 
> In core-connie.log, all messages were INFO and it appears all the connector 
> bundles were loaded.
> In core-persistence.log no issues (found data and left untouched)
> In core-rest.log it appears the WebApplicationContext initialized properly 
> (with completed message).  No errors. 
> 
> 
> Below is the full content of console.log
> 
> 14:31:09.478 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
> 14:31:09.486 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
> 14:31:09.495 ERROR 
> org.apache.syncope.client.console.SyncopeConsoleRequestCycleListener - 
> Exception found
> org.apache.wicket.WicketRuntimeException: Error attaching this container for 
> rendering: [WebMarkupContainer [Component id = body]]
> at 
> org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1837)
>  ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.onBeforeRender(Component.java:3916) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.internalBeforeRender(Component.java:950) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.beforeRender(Component.java:1018) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1825)
>  ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.onBeforeRender(Component.java:3916) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.internalBeforeRender(Component.java:950) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.beforeRender(Component.java:1018) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1825)
>  ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.onBeforeRender(Component.java:3916) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.internalBeforeRender(Component.java:950) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.beforeRender(Component.java:1018) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1825)
>  ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.onBeforeRender(Component.java:3916) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.markup.html.form.Form.onBeforeRender(Form.java:1807) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.internalBeforeRender(Component.java:950) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.beforeRender(Component.java:1018) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1825)
>  ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.onBeforeRender(Component.java:3916) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.internalBeforeRender(Component.java:950) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.beforeRender(Component.java:1018) 
> ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1825)
>  ~[wicket-core-7.7.0.jar:7.7.0]
> at 
> org.apache.wicket.Component.onBeforeRender(Component.java:3916) 
> 

Re: Syncope on AWS

2017-08-21 Thread Francesco Chicchiriccò

On 20/08/2017 14:43, John Stegeman wrote:

Hello All,


Hi John,
welcome to Apache Syncope :-)


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.


With which user are you logging into the Admin Console (or are you using 
with Swagger)? admin or other?


In order to understand what is happening, you should share the relevant 
snippets from your log files (core-* and console); in particular, please 
clear up all log files' content after logging into Admin Console, then 
attempt to access the Realms page and see what messages are added there.


Regards.

--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/



Syncope on AWS

2017-08-20 Thread John Stegeman
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