Hi Ghislain
thanks for redirecting the question to users list,
On 03/10/12 15:05, gbmamat wrote:
Hi,
Please, what are the persistent objects if you want to store in a database
all OAuth2.0 server information?
Typically, these are Client and ServerAccessToken which can have some
sub objects. Please note these are model classes only, they are the
'bridge' between the runtime and whatever persistence layer the
application has chosen to persist the actual data in, and thus do not
necessarily to be persisted 'as is'
In fact, I want to create a JDBC implementation of
AuthorizationCodeDataProvider interface.
Authorization code provider extends the data provider as it needs to
keep the transient user authorization confirmation details up until the
client requests a token in exchange for a grant. I guess one option is
to keep them in memory, using ehcache may be (to manage possible
overflows, etc) given that this data is supposed to be short-lived...
Though trying with JDBC should be a good start.
Let me know if you'd like to get more info,
Cheers, Sergey
Regards,
Ghislain
--
View this message in context:
http://cxf.547215.n5.nabble.com/Using-Database-to-store-OAuth2-0-server-informations-tp5715521.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
