Hi Vincent,
As you mentioned OAuth workflow couldn’t be totally stateless since server should remember the status of client workflow when the browser come back to the Agorava application.
This said, Agorava provides a stateless mode : a mode not tied to Http Session. By changing the OauthSession resolver you can use one of these mode (by using request parameter or a cookie).
Change the resolver in agoravara.propertes to activate the right mode as stated in the getting started doc :
http://agorava.org/doc/getting-started/ (check the « choose your OAuthSession resolver » section).
This said, I recommend that you use latest Agorava Snapshot because I corrected a lot of bugs in the resolver engine. you can access the 0.7.1-SNAPSHOT by adding this repo to your maven project pom.xml or your maven settings.xml :
<repository>
<id>agorava-snapshot-repo</id>
<name>Agorava Snapshot Repository</name>
<layout>default</layout>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
If you can wait a few days I should release next version next week, it’ll include these bug fixing.
Antoine