Hi Kalle, just wondering if you had a chance to take a look at making
federate work with 5.4. If there is something you feel I might be able to
assist with, please let me know. Thanks.
On Thu, Aug 21, 2014 at 11:14 AM, Kalle Korhonen wrote:
> Probably in the library if it happens right after cli
Okay I'll take a look over the weekend and see if I can figure it out.
Can't really promise I will though lol. Just an fyi, an up and coming
single sign on that might be worth including is amazon. It really helps if
you have an ecommerce site where you want to use amazon payment processing.
On Th
Probably in the library if it happens right after clicking on the link.
Kalle
On Thu, Aug 21, 2014 at 6:13 AM, George Christman
wrote:
> For the time being I was able to somewhat get things working by adding the
> js to my local META-INF directory. When I clicked the facebook link I
> received
For the time being I was able to somewhat get things working by adding the
js to my local META-INF directory. When I clicked the facebook link I
received a 400 error. Do you think this is a configuration error on my end,
or do you think it maybe a side effect of it not working in 5.4? I guess it
co
Unfortunately, I haven't updated federatedaccounts module to work with T5.4
yet. It's pretty simple as tapestry-security already supports T5.4 but will
be a week or two before I get to it because work's keeping me busy. Patches
welcome of course.
Kalle
On Wed, Aug 20, 2014 at 4:53 PM, George Chr
Hi Kalle, I'm getting the following exception,
*Unable to locate asset 'OauthSignIn.js' for component
registration/Signin:facebookoauthsignin. It should be located at
META-INF/assets/federated/OauthSignIn.js.*
*I'm using 5.4 and the following dependencies. Any thought wh
It's all sample code for typical use cases. For authentication, you need to
have (or Shiro needs to have) an AuthenticationInfo in session. That's
where the principals and the credentials tokens are stored. Separately, in
your Tapestry application, you may have several (preferably light) session
ob
I think where I was confused was coming at this with the idea of having a
database backed environment. I see your comments in CurrentUser.class
about ApplicationStateCreator
although I still don't fully understand it. I also seen some code where you
were commenting out
SimpleAuthenticationInfo wher
The examples lack comments because I strongly believe in self-documenting
code. FederatedAccountService.federate() is the core concept of the
federated account module. Federated accounts module allows you to federate
(i.e. join, merge) separate accounts together. The implementation of this
CurrentU
CurrentUser.class
Its a get method, probably on a hashtable-like object. Getting current
user.
The auth token is probably from the oauth2 provider like fb or gg.
With the current user and this token, merge them in *your* app.
/guessing
On 20/08/2014 7:05 am, "George Christman" wrote:
> I gue
I guess I'm not following the logic of the code then. Why would they be
passing CurrentUser into it then?
On Aug 19, 2014 4:46 PM, "Lance Java" wrote:
> The ApplicationStateManager is a core Tapestry service and is an
> abstraction over HttpSession persistence. As stated in the javadocs
> Applica
The ApplicationStateManager is a core Tapestry service and is an
abstraction over HttpSession persistence. As stated in the javadocs
Application state is probably a bad choice of naming. In hindsight it
should probably be called SessionStateManager.
On 19 Aug 2014 21:04, "George Christman" wrote:
12 matches
Mail list logo
