Well, you have to debug your federatedaccount service implementation, just put a breakpoint on the federate() call and see what you get. If you are using the built-in implementation classes, the typical issue to trip over is that you haven't configured or you've incorrectly configured the associated principal (see and understand contributions to federated account service: http://tynamo.org/tynamo-federatedaccounts+guide).
Kalle On Sat, Jul 28, 2012 at 6:12 PM, George Christman <gchrist...@cardaddy.com> wrote: > Hello, I'm trying to authenticate with a third party using Tapestry Security > Federate. > > I'm receiving the following error, however I don't know how to correct it. > > facebook account > error A Facebook federated user cannot be signed in, report this to support. > No account information found for authentication token > [AAAAADYIf8mQBAGaZCOiMQGStmQR6uOcjPuHcoTsRWb2jkERdKXZCZACsuCWaA08drmNnCAKZCrYJom8H6Ra0cpksVgCYbE8jfJkk8ZBKNVQZDZD] > by this Authenticator instance. Please check that it is configured > correctly. > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Tapestry-Security-Federate-Facebook-Exception-tp5714861.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
