Spring Security OAuth and Spring Security. UserDetails versus ClientDetails
OK, so I have built a custom UserDetails and UserDetailsService for our application(s). Some of the applications are web, some vert.x. In the vert.x world we can't include Spring Security or Spring Security Oauth for the server side stuff.
But we can create vert.x as a client app.
Anyway, if I am integrating both Spring Security and Spring Security Oauth (if they should even be integrated)
Do I need to create two different classes One for ClientDetails for OAuth stuff, and one UserDetails for SpringSecurity.
I think even for our web application, it should do OAuth for logging into the app, rather than standard Spring Security.
So if we just have OAuth, then I am guessing we only need ClientDetails and ClientDetailsService implementations and "toss out" our UserDetails and UserDetailsService implementations.
I was going to combine our UserDetails implementation to implement ClientDetails also, but the back end data storage (JDBC) would need to change.
Basically, If I am using Spring Security OAuth only, do I need the same fields and tables that I had with UserDetails object?