We are trying to convert a legacy Play 2.x framework web application to run on Quarkus with minimal-changes to the existing code base.
So far it looks like Renamed is a VERY close fit to the Play framework in terms of Routing and template processing which we hope would make it easy to move over to Quarkus.
However, when setting up the user security I ran into an issue. We are NOT using OIDC and only a JDBC backend. Reading the Renarde Security page it looks like I need to import the OIDC dependency.
Doing so and setting up my User class to implement RenardeUser when I try to restart Quarkus I get the error below.
It seems that by making my UserProvider also implement the OIDC provider interface fixes the build issue, but it seems I shouldn't need to do this if just using JWT/Database?
We are trying to convert a legacy Play 2.x framework web application to run on Quarkus with minimal-changes to the existing code base.
So far it looks like Renamed is a VERY close fit to the Play framework in terms of Routing and template processing which we hope would make it easy to move over to Quarkus.
However, when setting up the user security I ran into an issue. We are NOT using OIDC and only a JDBC backend. Reading the Renarde Security page it looks like I need to import the OIDC dependency.
Doing so and setting up my User class to implement RenardeUser when I try to restart Quarkus I get the error below.
It seems that by making my UserProvider also implement the OIDC provider interface fixes the build issue, but it seems I shouldn't need to do this if just using JWT/Database?
I am using Quarkus 2.12.2.Final and
Thanks..