Hi Team , I am currently working on a feature enhancement for Apache Guacamole (v1.5.5) and would appreciate your guidance. The requirement is to pass a custom string field (e.g., uniqueString) from the frontend UI to the backend and persist it in the Guacamole database using the native Java backend*.*
I would like to understand the recommended approach and the flow to achieve this while aligning with the architecture and design patterns followed in the existing codebase. What I am trying to do: - Capture a string field ( uniqueString ) from the UI. - Pass it through the REST layer. - Persist it in the database via the existing JDBC authentication extension (MySQL). - Follow the existing structure (e.g., how Connection, User, or History entries are handled) ? My Question: REST to Backend: What is the cleanest way to pass this to the Java backend while maintaining the decoupling between REST and JDBC layers? While attempting to implement this, I ran into an issue where adding guacamole-auth-jdbc as a dependency in the core guacamole module causes conflicts—especially around transitive dependencies and service injection. As per my understanding, the REST layer should not directly depend on JDBC. I believe this might violate the current architecture where data access is handled through UserContext, Directory, and associated factories but they seem to be complex . Thanks , S Kaur
