mert-z / spring-oauth2-cassandra-token-store Goto Github PK

If the access token is under validity, I am able to get a new access token using refresh token.
If the access token expires, I am not able to get a new one using same refresh token.

The problem occurs in the method removeAccessTokenUsingRefreshToken of CassandraStore class, where the access token ie returned null.

That will avoid so many inserts on multiple tables and decrease the risk of having stale/unsync data between tables. On the other hand this will require migration of existing data to the new schema which can be costly.

Hi, will there be a version for the latest spring-data-cassandra:2.0.x version?
I think your example is better than
https://github.com/welovelain/spring-security-oauth2-cassandra-utils
, but outdated

Current implementation involves a READ before adding access tokens to "usernameToAccessTokenRepository" and "clientIdToAccessTokenRepository" repositories. Instead a new access token can be inserted to a set using the UPDATE command and the addition (+) operator (See Using the set type).

Ex;
UPDATE uname_to_access SET oAuth2AccessTokenSet = oAuth2AccessTokenSet + {'new_access_token'} WHERE key = 'clientId:userName';

Afais, current implementation for "spring-data-cassandra" doesn't provide an API to update a collection. So we may end up implementing custom repository methods for this however we may also need to find a way to wire the underlying UPDATE statement into an existing BATCH list of statements.

Enhacement issue for better performance. Refers to the operations in lines listed below;

• spring-oauth2-cassandra-token-store/src/main/java/mertz/security/oauth2/provider/token/store/cassandra/CassandraTokenStore.java

  Line 204 in c09dff1

  // Delete from UsernameToAccessToken table

• spring-oauth2-cassandra-token-store/src/main/java/mertz/security/oauth2/provider/token/store/cassandra/CassandraTokenStore.java

  Line 211 in c09dff1

  // Delete from ClientIdToAccessToken table