Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CDSToolkit] - Ob 300 Refresh token Validity period issue #192

Closed
Akila94 opened this issue Nov 8, 2024 · 2 comments
Closed

[CDSToolkit] - Ob 300 Refresh token Validity period issue #192

Akila94 opened this issue Nov 8, 2024 · 2 comments

Comments

@Akila94
Copy link
Member

Akila94 commented Nov 8, 2024

According to OB 200 behavior, the sharing_duration value should set the refresh token validity period. However, in OB 300, the refresh token validity period is determined by the service provider's configured value. We reviewed the OB 300 implementation and identified that setRefreshTokenValidityPeriod is set at the code level. Additionally, when examining the database, we found the REFRESH_TOKEN_VALIDITY_PERIOD in the IDN_OAUTH2_ACCESS_TOKEN table is set to '86400000'.

This appears to be a system issue. We would appreciate your input.

[1]https://github.com/wso2/reference-implementation-consumerdatastandards-au/blob/6dd827d6efd79e5de453daa1a6bac5c0bc854b45/components/org.wso2.openbanking.cds.identity/src/main/java/org/wso2/openbanking/cds/identity/grant/type/handlers/CDSAuthorizationCodeGrantHandler.java#L123C36-L123C65

@Akila94
Copy link
Member Author

Akila94 commented Nov 8, 2024

@Akila94
Copy link
Member Author

Akila94 commented Nov 8, 2024

Verified as fixed

@Akila94 Akila94 closed this as completed Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant