5 Open Issues Need Help Last updated: Jul 14, 2025

Open Issues Need Help

View All on GitHub
Token Refresh Handling about 2 months ago

AI Summary: Implement token refresh functionality for the LinkSphere application. This involves storing refresh tokens after login, using them to obtain new access tokens when the latter expire via a POST request to the specified endpoint, and updating the stored tokens accordingly. The goal is to maintain user sessions without requiring re-authentication.

Complexity: 4/5
enhancement good first issue refactor
User Profile Management about 2 months ago

AI Summary: Implement user profile management functionality, allowing users to update their name, email, and password. This involves integrating with Keycloak's REST APIs for user retrieval and updates, handling authentication (admin token or token introspection), and creating a frontend interface using the profile-page endpoint. The changes must be reflected in Keycloak.

Complexity: 4/5
enhancement good first issue refactor

AI Summary: This task involves refactoring the notification service from the main application into a standalone, deployable component. This includes separating the notification logic, deploying it to a platform like Render, and then updating the main application to connect to the newly deployed service.

Complexity: 4/5
good first issue refactor

AI Summary: The task involves configuring Keycloak to use a PostgreSQL database for persistent storage instead of its default in-memory storage. This requires provisioning a PostgreSQL database (already done), and updating the Keycloak Docker configuration with the correct database connection details (host, port, username, password, and database name). The Keycloak documentation will be a key resource for this task.

Complexity: 4/5
enhancement good first issue refactor
Logout Intergration about 2 months ago

AI Summary: Implement a secure logout functionality that clears frontend tokens, sends a logout request to Keycloak's `/realms/myapp-realm/protocol/openid-connect/logout` endpoint with refresh token and client ID, and redirects the user to the login screen. The logout must invalidate the Keycloak session.

Complexity: 3/5
enhancement good first issue refactor