Re: [ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

[Borut Bolčina]

Turning on debug wire level

reveals some data, but only small responses from fb are logged.

No error messages receiving, logged in to facebook and local app, just a
dialog which should close is still open presenting 500 error.

After inspecting the communication with wireshark on port 443, I do get
some larger chunks of encrypted data. Maybe
tynamo-federatedaccounts-facebook has some logging - will investigate.



2013/11/25 Dmitry Gusev 

> Hi,
>
> I suspect you have some error and what you're receiving in your header is a
> stacktrace or some error message/page.
>
> After you increased your header size, can you grab the traffic with some
> sniffer to see what's in there?
>
>
>
>
> On Mon, Nov 25, 2013 at 1:25 PM, Borut Bolčina  >wrote:
>
> > Hi again,
> >
> > when using returnPageName I initially encountered a problem because our
> > custom url encoder was interfering with generated return uris.
> >
> > When custom url encoder is not used, the authentication process comes a
> > bit further now. I get the user info back from fb, but the dialog does
> not
> > close as there is a run time exception:
> > WARN:oejs.AbstractHttpConnection:header full: java.lang.RuntimeException:
> > Header>6144
> >
> > Resolved this by configuring jetty maven plugin with header sizes
> >
> > 
> >  > implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
> > 80
> > 6
> > 16000
> > 1
> > 
> > 
> >
> > but I was wondering what is causing headers larger then 6k bytes?
> >
> >
> >
> >
> >
> > 2013/11/22 Borut Bolčina 
> >
> >> Thanks for additional info.
> >>
> >> Now, I have successfully managed to create a facebook login flow with
> >> 0.2.0 version by using:
> >>
> >> In AppModule:
> >> configuration.add(FederatedAccountSymbols.SUCCESSURL,
> >> "/PrijavaRedirect"); //0.2.0
> >>
> >> At Login.tml
> >> 
> >>
> >>
> >> And a redirect page:
> >>
> >> public class PrijavaRedirect {
> >> @Inject
> >> private Logger logger;
> >>
> >> @Inject
> >> private LoginContextService loginContextService;
> >>
> >> public Object onActivate(EventContext ec) {
> >> String requestUri = loginContextService.getSuccessPage();
> >> logger.debug("Saved request url {}",
> >> loginContextService.getSuccessPage());
> >> if (!requestUri.startsWith("/")) {
> >> requestUri = "/" + requestUri;
> >> }
> >> try {
> >> loginContextService.redirectToSavedRequest(requestUri);
> >> return null;
> >> } catch (Exception e) {
> >> e.printStackTrace();
> >> }
> >> return loginContextService.getSuccessPage();
> >>
> >> }
> >> }
> >>
> >> The drawback of this flow is quite nasty, as this white almost blank
> page
> >> gets displayed for users.
> >>
> >> I tried now with version 0.4.3
> >>
> >> In AppModule:
> >> configuration.add(FederatedAccountSymbols.DEFAULT_RETURNPAGE,
> >> "PrijavaRedirect"); // 0.4.3
> >>
> >> At Login.tml
> >> 
> >>
> >> But when run, I get
> >> [09:50:38] ERROR
> >> [org.tynamo.security.federatedaccounts.facebook.pages.FacebookOauth]:
> >> Facebook access_token request returned status code 400
> >>
> >> and the facebook dialog AFTER a FB login looks like:
> >> [image: Slika v vrstici 1]
> >>
> >> My hosts file is the same for both cases:
> >> 127.0.0.1   najdi.si
> >>
> >> I will now try to use the new parameter returnPageName without this
> >> LoginRedirect page and see if it works.
> >>
> >>
> >>
> >> 2013/11/21 Alejandro Scandroli 
> >>
> >>> Hi Borut
> >>>
> >>>
> >>> The FacebookOauthSignIn has a new parameter "returnPageName".
> >>> If the parameter is not specified the component will use the value of
> >>> the FederatedAccountSymbols.DEFAULT_RETURNPAGE symbol.
> >>>
> >>> Alejandro.
> >>>
> >>> On Thu, Nov 21, 2013 at 12:17 PM, Borut Bolčina <
> borut.bolc...@gmail.com>
> >>> wrote:
> >>> > And indeed in 0.4.3 there is a class with commented field. How to
> >>> replace
> >>> > this functionality?
> >>> >
> >>> > public class FederatedAccountSymbols {
> >>> > // public static final String SUCCESSURL =
> >>> > "federatedaccounts.successurl";
> >>> >
> >>> > public static final String COMMITAFTER_OAUTH =
> >>> > "federatedaccounts.commitafteroauth";
> >>> >
> >>> > public static final String HTTPCLIENT_ON_GAE = "httpclient.gae";
> >>> >
> >>> > public static final String DEFAULT_RETURNPAGE =
> >>> > "federatedaccounts.default_returnpage";
> >>> >
> >>> > public static final String DEFAULT_REMEMBERME =
> >>> > "federatedaccounts.default_rememberme";
> >>> >
> >>> > public static final String LOCALACCOUNT_REALMNAME =
> >>> > "federatedaccounts.localaccount_realmname";
> >>> > }
> >>> >
> >>> >
> >>> > 2013/11/21 Borut Bolčina 
> >>> >
> >>> >> Yes, indeed, another dependent project brought in the 0.2.0 version
> of
> >>> >> federatedaccounts-core.
> >>> >>
> >>> >> Now I am having another issue:
> >>> >> configuration.add

Re: [ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

[Dmitry Gusev]

Hi,

I suspect you have some error and what you're receiving in your header is a
stacktrace or some error message/page.

After you increased your header size, can you grab the traffic with some
sniffer to see what's in there?




On Mon, Nov 25, 2013 at 1:25 PM, Borut Bolčina wrote:

> Hi again,
>
> when using returnPageName I initially encountered a problem because our
> custom url encoder was interfering with generated return uris.
>
> When custom url encoder is not used, the authentication process comes a
> bit further now. I get the user info back from fb, but the dialog does not
> close as there is a run time exception:
> WARN:oejs.AbstractHttpConnection:header full: java.lang.RuntimeException:
> Header>6144
>
> Resolved this by configuring jetty maven plugin with header sizes
>
> 
>  implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
> 80
> 6
> 16000
> 1
> 
> 
>
> but I was wondering what is causing headers larger then 6k bytes?
>
>
>
>
>
> 2013/11/22 Borut Bolčina 
>
>> Thanks for additional info.
>>
>> Now, I have successfully managed to create a facebook login flow with
>> 0.2.0 version by using:
>>
>> In AppModule:
>> configuration.add(FederatedAccountSymbols.SUCCESSURL,
>> "/PrijavaRedirect"); //0.2.0
>>
>> At Login.tml
>> 
>>
>>
>> And a redirect page:
>>
>> public class PrijavaRedirect {
>> @Inject
>> private Logger logger;
>>
>> @Inject
>> private LoginContextService loginContextService;
>>
>> public Object onActivate(EventContext ec) {
>> String requestUri = loginContextService.getSuccessPage();
>> logger.debug("Saved request url {}",
>> loginContextService.getSuccessPage());
>> if (!requestUri.startsWith("/")) {
>> requestUri = "/" + requestUri;
>> }
>> try {
>> loginContextService.redirectToSavedRequest(requestUri);
>> return null;
>> } catch (Exception e) {
>> e.printStackTrace();
>> }
>> return loginContextService.getSuccessPage();
>>
>> }
>> }
>>
>> The drawback of this flow is quite nasty, as this white almost blank page
>> gets displayed for users.
>>
>> I tried now with version 0.4.3
>>
>> In AppModule:
>> configuration.add(FederatedAccountSymbols.DEFAULT_RETURNPAGE,
>> "PrijavaRedirect"); // 0.4.3
>>
>> At Login.tml
>> 
>>
>> But when run, I get
>> [09:50:38] ERROR
>> [org.tynamo.security.federatedaccounts.facebook.pages.FacebookOauth]:
>> Facebook access_token request returned status code 400
>>
>> and the facebook dialog AFTER a FB login looks like:
>> [image: Slika v vrstici 1]
>>
>> My hosts file is the same for both cases:
>> 127.0.0.1   najdi.si
>>
>> I will now try to use the new parameter returnPageName without this
>> LoginRedirect page and see if it works.
>>
>>
>>
>> 2013/11/21 Alejandro Scandroli 
>>
>>> Hi Borut
>>>
>>>
>>> The FacebookOauthSignIn has a new parameter "returnPageName".
>>> If the parameter is not specified the component will use the value of
>>> the FederatedAccountSymbols.DEFAULT_RETURNPAGE symbol.
>>>
>>> Alejandro.
>>>
>>> On Thu, Nov 21, 2013 at 12:17 PM, Borut Bolčina 
>>> wrote:
>>> > And indeed in 0.4.3 there is a class with commented field. How to
>>> replace
>>> > this functionality?
>>> >
>>> > public class FederatedAccountSymbols {
>>> > // public static final String SUCCESSURL =
>>> > "federatedaccounts.successurl";
>>> >
>>> > public static final String COMMITAFTER_OAUTH =
>>> > "federatedaccounts.commitafteroauth";
>>> >
>>> > public static final String HTTPCLIENT_ON_GAE = "httpclient.gae";
>>> >
>>> > public static final String DEFAULT_RETURNPAGE =
>>> > "federatedaccounts.default_returnpage";
>>> >
>>> > public static final String DEFAULT_REMEMBERME =
>>> > "federatedaccounts.default_rememberme";
>>> >
>>> > public static final String LOCALACCOUNT_REALMNAME =
>>> > "federatedaccounts.localaccount_realmname";
>>> > }
>>> >
>>> >
>>> > 2013/11/21 Borut Bolčina 
>>> >
>>> >> Yes, indeed, another dependent project brought in the 0.2.0 version of
>>> >> federatedaccounts-core.
>>> >>
>>> >> Now I am having another issue:
>>> >> configuration.add(FederatedAccountSymbols.SUCCESSURL,
>>> "/prijavaRedirect");
>>> >>
>>> >> SUCCESSURL is not a field anymore.
>>> >>
>>> >>
>>> >> 2013/11/21 Kalle Korhonen 
>>> >>
>>> >>> At a first glance, it'd  looks like federatedaccounts-core in your
>>> >>> classpath is a pre 0.4 version, based on:
>>> >>> "Type
>>> >>>
>>> >>>
>>> org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
>>> >>> not present"
>>> >>>
>>> >>> Is it possible you have multiple versions of the relevant libraries
>>> in
>>> >>> your
>>> >>> classpath?
>>> >>>
>>> >>> Kalle
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Wed, Nov 20, 2013 at 11:41 PM, Borut Bolčina <
>>> borut.bolc...@gmail.com
>>> >>> >wrote:
>>> >>>
>>> >>> > Hi Kalle,
>>> >>> >
>>> >>> > I just tried the 0.4.3 version (before 

Re: [ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

[Alejandro Scandroli]

Hi Borut


The FacebookOauthSignIn has a new parameter "returnPageName".
If the parameter is not specified the component will use the value of
the FederatedAccountSymbols.DEFAULT_RETURNPAGE symbol.

Alejandro.

On Thu, Nov 21, 2013 at 12:17 PM, Borut Bolčina  wrote:
> And indeed in 0.4.3 there is a class with commented field. How to replace
> this functionality?
>
> public class FederatedAccountSymbols {
> // public static final String SUCCESSURL =
> "federatedaccounts.successurl";
>
> public static final String COMMITAFTER_OAUTH =
> "federatedaccounts.commitafteroauth";
>
> public static final String HTTPCLIENT_ON_GAE = "httpclient.gae";
>
> public static final String DEFAULT_RETURNPAGE =
> "federatedaccounts.default_returnpage";
>
> public static final String DEFAULT_REMEMBERME =
> "federatedaccounts.default_rememberme";
>
> public static final String LOCALACCOUNT_REALMNAME =
> "federatedaccounts.localaccount_realmname";
> }
>
>
> 2013/11/21 Borut Bolčina 
>
>> Yes, indeed, another dependent project brought in the 0.2.0 version of
>> federatedaccounts-core.
>>
>> Now I am having another issue:
>> configuration.add(FederatedAccountSymbols.SUCCESSURL, "/prijavaRedirect");
>>
>> SUCCESSURL is not a field anymore.
>>
>>
>> 2013/11/21 Kalle Korhonen 
>>
>>> At a first glance, it'd  looks like federatedaccounts-core in your
>>> classpath is a pre 0.4 version, based on:
>>> "Type
>>>
>>> org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
>>> not present"
>>>
>>> Is it possible you have multiple versions of the relevant libraries in
>>> your
>>> classpath?
>>>
>>> Kalle
>>>
>>>
>>>
>>> On Wed, Nov 20, 2013 at 11:41 PM, Borut Bolčina >> >wrote:
>>>
>>> > Hi Kalle,
>>> >
>>> > I just tried the 0.4.3 version (before I had 0.2.0) and I get this
>>> > exception below. Is there something quick I can fix in my code?
>>> >
>>> > 2013-11-20 17:00:57.566:WARN:oejuc.AbstractLifeCycle:FAILED app:
>>> > java.lang.RuntimeException: Exception loading module(s) from manifest
>>> >
>>> >
>>> jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
>>> > Failure loading Tapestry IoC module class
>>> >
>>> >
>>> org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
>>> > Type
>>> >
>>> >
>>> org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
>>> > not present
>>> > java.lang.RuntimeException: Exception loading module(s) from manifest
>>> >
>>> >
>>> jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
>>> > Failure loading Tapestry IoC module class
>>> >
>>> >
>>> org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
>>> > Type
>>> >
>>> >
>>> org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
>>> > not present
>>> > at
>>> >
>>> >
>>> org.apache.tapestry5.ioc.IOCUtilities.addModulesInManifest(IOCUtilities.java:123)
>>> > at
>>> >
>>> >
>>> org.apache.tapestry5.ioc.IOCUtilities.addDefaultModules(IOCUtilities.java:77)
>>> > at
>>> >
>>> >
>>> org.apache.tapestry5.internal.TapestryAppInitializer.(TapestryAppInitializer.java:124)
>>> > at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:103)
>>> > at
>>> > org.eclipse.jetty.servlet.FilterHolder.doStart(FilterHolder.java:119)
>>> > at
>>> >
>>> >
>>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>>> > at
>>> >
>>> >
>>> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:719)
>>> > at
>>> >
>>> >
>>> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
>>> > at
>>> >
>>> >
>>> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
>>> > at
>>> >
>>> >
>>> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:710)
>>> > at
>>> > org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
>>> > at
>>> >
>>> >
>>> org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:293)
>>> > at
>>> >
>>> >
>>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>>> > at
>>> >
>>> >
>>> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
>>> > at
>>> >
>>> >
>>> org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:172)
>>> > at
>>> >
>>> >
>>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>>> > at
>>> >
>>> >
>>> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
>>> > at
>>> >
>>> >
>>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLife

Re: [ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

[Borut Bolčina]

And indeed in 0.4.3 there is a class with commented field. How to replace
this functionality?

public class FederatedAccountSymbols {
// public static final String SUCCESSURL =
"federatedaccounts.successurl";

public static final String COMMITAFTER_OAUTH =
"federatedaccounts.commitafteroauth";

public static final String HTTPCLIENT_ON_GAE = "httpclient.gae";

public static final String DEFAULT_RETURNPAGE =
"federatedaccounts.default_returnpage";

public static final String DEFAULT_REMEMBERME =
"federatedaccounts.default_rememberme";

public static final String LOCALACCOUNT_REALMNAME =
"federatedaccounts.localaccount_realmname";
}


2013/11/21 Borut Bolčina 

> Yes, indeed, another dependent project brought in the 0.2.0 version of
> federatedaccounts-core.
>
> Now I am having another issue:
> configuration.add(FederatedAccountSymbols.SUCCESSURL, "/prijavaRedirect");
>
> SUCCESSURL is not a field anymore.
>
>
> 2013/11/21 Kalle Korhonen 
>
>> At a first glance, it'd  looks like federatedaccounts-core in your
>> classpath is a pre 0.4 version, based on:
>> "Type
>>
>> org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
>> not present"
>>
>> Is it possible you have multiple versions of the relevant libraries in
>> your
>> classpath?
>>
>> Kalle
>>
>>
>>
>> On Wed, Nov 20, 2013 at 11:41 PM, Borut Bolčina > >wrote:
>>
>> > Hi Kalle,
>> >
>> > I just tried the 0.4.3 version (before I had 0.2.0) and I get this
>> > exception below. Is there something quick I can fix in my code?
>> >
>> > 2013-11-20 17:00:57.566:WARN:oejuc.AbstractLifeCycle:FAILED app:
>> > java.lang.RuntimeException: Exception loading module(s) from manifest
>> >
>> >
>> jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
>> > Failure loading Tapestry IoC module class
>> >
>> >
>> org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
>> > Type
>> >
>> >
>> org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
>> > not present
>> > java.lang.RuntimeException: Exception loading module(s) from manifest
>> >
>> >
>> jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
>> > Failure loading Tapestry IoC module class
>> >
>> >
>> org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
>> > Type
>> >
>> >
>> org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
>> > not present
>> > at
>> >
>> >
>> org.apache.tapestry5.ioc.IOCUtilities.addModulesInManifest(IOCUtilities.java:123)
>> > at
>> >
>> >
>> org.apache.tapestry5.ioc.IOCUtilities.addDefaultModules(IOCUtilities.java:77)
>> > at
>> >
>> >
>> org.apache.tapestry5.internal.TapestryAppInitializer.(TapestryAppInitializer.java:124)
>> > at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:103)
>> > at
>> > org.eclipse.jetty.servlet.FilterHolder.doStart(FilterHolder.java:119)
>> > at
>> >
>> >
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>> > at
>> >
>> >
>> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:719)
>> > at
>> >
>> >
>> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
>> > at
>> >
>> >
>> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
>> > at
>> >
>> >
>> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:710)
>> > at
>> > org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
>> > at
>> >
>> >
>> org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:293)
>> > at
>> >
>> >
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>> > at
>> >
>> >
>> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
>> > at
>> >
>> >
>> org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:172)
>> > at
>> >
>> >
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>> > at
>> >
>> >
>> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
>> > at
>> >
>> >
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>> > at
>> >
>> >
>> org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
>> > at org.eclipse.jetty.server.Server.doStart(Server.java:280)
>> > at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
>> > at
>> >
>> >
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>> > at
>> >
>> >
>> org.mortbay.jetty.plugin.Abstract

Re: [ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

[Borut Bolčina]

Yes, indeed, another dependent project brought in the 0.2.0 version of
federatedaccounts-core.

Now I am having another issue:
configuration.add(FederatedAccountSymbols.SUCCESSURL, "/prijavaRedirect");

SUCCESSURL is not a field anymore.


2013/11/21 Kalle Korhonen 

> At a first glance, it'd  looks like federatedaccounts-core in your
> classpath is a pre 0.4 version, based on:
> "Type
>
> org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
> not present"
>
> Is it possible you have multiple versions of the relevant libraries in your
> classpath?
>
> Kalle
>
>
>
> On Wed, Nov 20, 2013 at 11:41 PM, Borut Bolčina  >wrote:
>
> > Hi Kalle,
> >
> > I just tried the 0.4.3 version (before I had 0.2.0) and I get this
> > exception below. Is there something quick I can fix in my code?
> >
> > 2013-11-20 17:00:57.566:WARN:oejuc.AbstractLifeCycle:FAILED app:
> > java.lang.RuntimeException: Exception loading module(s) from manifest
> >
> >
> jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
> > Failure loading Tapestry IoC module class
> >
> >
> org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
> > Type
> >
> >
> org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
> > not present
> > java.lang.RuntimeException: Exception loading module(s) from manifest
> >
> >
> jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
> > Failure loading Tapestry IoC module class
> >
> >
> org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
> > Type
> >
> >
> org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
> > not present
> > at
> >
> >
> org.apache.tapestry5.ioc.IOCUtilities.addModulesInManifest(IOCUtilities.java:123)
> > at
> >
> >
> org.apache.tapestry5.ioc.IOCUtilities.addDefaultModules(IOCUtilities.java:77)
> > at
> >
> >
> org.apache.tapestry5.internal.TapestryAppInitializer.(TapestryAppInitializer.java:124)
> > at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:103)
> > at
> > org.eclipse.jetty.servlet.FilterHolder.doStart(FilterHolder.java:119)
> > at
> >
> >
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> > at
> >
> >
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:719)
> > at
> >
> >
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
> > at
> >
> >
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
> > at
> >
> >
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:710)
> > at
> > org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
> > at
> >
> >
> org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:293)
> > at
> >
> >
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> > at
> >
> >
> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
> > at
> >
> >
> org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:172)
> > at
> >
> >
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> > at
> >
> >
> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
> > at
> >
> >
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> > at
> >
> >
> org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
> > at org.eclipse.jetty.server.Server.doStart(Server.java:280)
> > at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
> > at
> >
> >
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> > at
> >
> >
> org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:520)
> > at
> >
> >
> org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:365)
> > at
> org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:523)
> > at
> >
> >
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> > at
> >
> >
> org.apache.maven.lifecycle.internal.Life

Re: [ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

[Kalle Korhonen]

At a first glance, it'd  looks like federatedaccounts-core in your
classpath is a pre 0.4 version, based on:
"Type
org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
not present"

Is it possible you have multiple versions of the relevant libraries in your
classpath?

Kalle



On Wed, Nov 20, 2013 at 11:41 PM, Borut Bolčina wrote:

> Hi Kalle,
>
> I just tried the 0.4.3 version (before I had 0.2.0) and I get this
> exception below. Is there something quick I can fix in my code?
>
> 2013-11-20 17:00:57.566:WARN:oejuc.AbstractLifeCycle:FAILED app:
> java.lang.RuntimeException: Exception loading module(s) from manifest
>
> jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
> Failure loading Tapestry IoC module class
>
> org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
> Type
>
> org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
> not present
> java.lang.RuntimeException: Exception loading module(s) from manifest
>
> jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
> Failure loading Tapestry IoC module class
>
> org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
> Type
>
> org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
> not present
> at
>
> org.apache.tapestry5.ioc.IOCUtilities.addModulesInManifest(IOCUtilities.java:123)
> at
>
> org.apache.tapestry5.ioc.IOCUtilities.addDefaultModules(IOCUtilities.java:77)
> at
>
> org.apache.tapestry5.internal.TapestryAppInitializer.(TapestryAppInitializer.java:124)
> at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:103)
> at
> org.eclipse.jetty.servlet.FilterHolder.doStart(FilterHolder.java:119)
> at
>
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
>
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:719)
> at
>
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
> at
>
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
> at
>
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:710)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
> at
>
> org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:293)
> at
>
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
>
> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
> at
>
> org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:172)
> at
>
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
>
> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
> at
>
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
>
> org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
> at org.eclipse.jetty.server.Server.doStart(Server.java:280)
> at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
> at
>
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at
>
> org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:520)
> at
>
> org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:365)
> at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:523)
> at
>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.c

Re: [ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

[Borut Bolčina]

Hi Kalle,

I just tried the 0.4.3 version (before I had 0.2.0) and I get this
exception below. Is there something quick I can fix in my code?

2013-11-20 17:00:57.566:WARN:oejuc.AbstractLifeCycle:FAILED app:
java.lang.RuntimeException: Exception loading module(s) from manifest
jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
Failure loading Tapestry IoC module class
org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
Type
org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
not present
java.lang.RuntimeException: Exception loading module(s) from manifest
jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
Failure loading Tapestry IoC module class
org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
Type
org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
not present
at
org.apache.tapestry5.ioc.IOCUtilities.addModulesInManifest(IOCUtilities.java:123)
at
org.apache.tapestry5.ioc.IOCUtilities.addDefaultModules(IOCUtilities.java:77)
at
org.apache.tapestry5.internal.TapestryAppInitializer.(TapestryAppInitializer.java:124)
at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:103)
at org.eclipse.jetty.servlet.FilterHolder.doStart(FilterHolder.java:119)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at
org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:719)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:710)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
at
org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:293)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:172)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at
org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
at org.eclipse.jetty.server.Server.doStart(Server.java:280)
at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:520)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:365)
at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:523)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)

Re: [ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

[Howard Lewis Ship]

Terrific work as always!


On Thu, Aug 22, 2013 at 4:43 PM, Kalle Korhonen
wrote:

> Federatedaccounts takes another leap forward by integrating with a new,
> Scribe-based module, Pac4j by Jérôme Leleu <
> https://github.com/leleuj/pac4j>.
> See, the problem with Scribe, and Oauth in general, is that there's no
> standard way of getting any unique identifier with Oauth (unlike in
> OpenID). So there are several different provider specific extension and it
> quickly becomes a mess (read what the author of Scribe thinks about
> this<
> https://github.com/fernandezpablo85/scribe-java/wiki/Scribe-scope-revised
> >).
> Anyway, it's great somebody, and in this case, Jérôme, still bothers to
> generalize the approach because otherwise I would have needed to do it. The
> new Federated Accounts module, tynamo-federatedaccounts-pac4jbasedoauth,
> simply provides UI components (Oauth sign in components, callback pages)
> around Pac4j, handles the Oauth all automatically and bakes in
> Tapestry-style configuration around it so all you need to do is to just add
> your Oauth app credentials for your provider of choice. The primary use
> case for the new module is authentication and user profile federation, for
> other uses cases, you typically still want to use provider specific APIs
> and libraries. Documentation is also updated although a bit thin still.
> Read more at tynamo-federatedaccounts
> guide<
> http://docs.codehaus.org/display/TYNAMO/tynamo-federatedaccounts+guide>
> .
>
> Release notes:
> Improvement
>
>- [TYNAMO-211 ] - Allow
>parametrized configuration in federated login components for setting
>rememberMe in the token
>- [TYNAMO-220 ] - Implement
>rolling tokens support for federated accounts
>- [TYNAMO-181 ] - Implement
>DefaultJpaFederatedAccountServiceImpl
>- [TYNAMO-182 ] - Support
>GitHub federated login
>
> New Feature
>
>- [TYNAMO-93 ] - Support for
>Google OAuth 2.0
>
> Bug
>
>- [TYNAMO-217 ] -
>returnPageName is required since there's no defaultReturnPage prop in
>AbstractOauthSignIn
>
>
> Enjoy,
>
> Tynamo Team
>



-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

[ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

[Kalle Korhonen]

Federatedaccounts takes another leap forward by integrating with a new,
Scribe-based module, Pac4j by Jérôme Leleu .
See, the problem with Scribe, and Oauth in general, is that there's no
standard way of getting any unique identifier with Oauth (unlike in
OpenID). So there are several different provider specific extension and it
quickly becomes a mess (read what the author of Scribe thinks about
this).
Anyway, it's great somebody, and in this case, Jérôme, still bothers to
generalize the approach because otherwise I would have needed to do it. The
new Federated Accounts module, tynamo-federatedaccounts-pac4jbasedoauth,
simply provides UI components (Oauth sign in components, callback pages)
around Pac4j, handles the Oauth all automatically and bakes in
Tapestry-style configuration around it so all you need to do is to just add
your Oauth app credentials for your provider of choice. The primary use
case for the new module is authentication and user profile federation, for
other uses cases, you typically still want to use provider specific APIs
and libraries. Documentation is also updated although a bit thin still.
Read more at tynamo-federatedaccounts
guide
.

Release notes:
Improvement

   - [TYNAMO-211 ] - Allow
   parametrized configuration in federated login components for setting
   rememberMe in the token
   - [TYNAMO-220 ] - Implement
   rolling tokens support for federated accounts
   - [TYNAMO-181 ] - Implement
   DefaultJpaFederatedAccountServiceImpl
   - [TYNAMO-182 ] - Support
   GitHub federated login

New Feature

   - [TYNAMO-93 ] - Support for
   Google OAuth 2.0

Bug

   - [TYNAMO-217 ] -
   returnPageName is required since there's no defaultReturnPage prop in
   AbstractOauthSignIn


Enjoy,

Tynamo Team