Be able to have private/public key when using smallrye-jwt extension on dev mode

[mcruzdev]

Description

Actually, we need to generate a public key in Dev mode to develop with the extension. It would be greate if we have a way to do not worry about it on dev mode.

Implementation ideas

No response

[quarkus-bot]

/cc @Ladicek (smallrye), @jmartisk (smallrye), @phillip-kruger (smallrye), @radcortez (smallrye), @sberyozkin (jwt)

[sberyozkin]

Thanks @mcruzdev Good idea, and I recall, @FroMage proposed something similar.

The question is how to use the private key in devmode.
In devmode, quarkus-smallrye-jwt devservice should allocate a key pair and set mp.jwt.verify.publickey but also smallrye.jwt.sign.key for the quarkus-smallrye-jwt-build be able to use it to generate tokens.

It should indeed make it easier to run the quickstart.

But additionally, we can consider adding Dev UI support for users be able to select which claims should be added to the generated token and then use this token to test the service.

[mcruzdev]

Thank you for the quick response @sberyozkin!

Just to increment the proposal:

1. Add a codestart on (quarkus-smallrye-jwt and quarkus-smallrye-jwt-build) with simple sample code

2. In devmode, quarkus-smallrye-jwt devservice should allocate a key pair and set mp.jwt.verify.publickey but also smallrye.jwt.sign.key for the quarkus-smallrye-jwt-build be able to use it to generate tokens.

3. Add the DevUI allowing the user to add claims and groups to the token and get the token in a easy way.

[mcruzdev]

Having this proposal approved, can I start to contribute with this issue?

[sberyozkin]

@mcruzdev You are welcome to start, thanks.

Can I propose to start first with generating an in-mem key pair as you proposed and set the suggested properties and confirm that is sufficient for the smallrye-jwt quickstart demo to work in devmode and when running tests, without having to manually set the keys ?
Note though it can be done if none of the smallrye-jwt verification properties is already set, and none of the smallrye-jwt-build signing key properties are set

Thanks

[mcruzdev]

Great! Thank you for this suggestion!

[michalvavrik]

@FroMage proposed something similar

#22182 ?

[sberyozkin]

That was a CLI level enhancement, which is worth completing (minus EC keys for now), but Steph was talking about the key pair in devmode, he may have done something related in Renarde

[michalvavrik]

That was a CLI level enhancement, which is worth completing (minus EC keys for now), but Steph was talking about the key pair in devmode, he may have done something related in Renarde

got it, thanks

[FroMage]

Yup: https://github.com/quarkiverse/quarkus-renarde/blob/main/deployment/src/main/java/io/quarkiverse/renarde/deployment/RenardeProcessor.java#L267

IMO this should be done by JWT as a build step, I don't see why you need a dev service for that.