This version (2017/05/27 13:44) is a draft.
Approvals: 0/1

[09:52:12] * ChanServ sets mode: +o purplefox [12:15:27] <aesteve> hi folks :) [12:56:24] * ChanServ sets mode: +o purplefox

[15:23:32] <BadApe> trying to get jwt working, io.vertx.ext.web.handler.impl.JWTAuthHandlerImpl No Authorization header was found i can see the token in the header as id_token

[15:23:42] <BadApe> what should the header name be?

[15:25:45] <BadApe> oh i figured it out

[17:52:57] <AlexLehm> purplefox, temporal_: any change of checking my prs for mail yet?

[18:47:42] <AlexLehm> chance

[19:16:44] <BadApe> hello, i just noticed that the wiki pages linked from: ( and are missing

[19:17:17] <BadApe> i think they contain the information i need to know why my log is full of 2016-02-13 18:14:04 INFO io.vertx.ext.auth.jwt.impl.JWT HS256 not available

[19:17:19] <BadApe> etc

[19:21:46] <temporal_> BadApe can you open an issue on vertx-stack project ?

[19:34:42] <AlexLehm> BadApe: these are methods from the jdk, so you should be able to find them on the normal javadoc

[19:34:56] <AlexLehm> javax.crypto.Mac

[19:37:17] <AlexLehm> you can ignore the log messages though I think

[19:40:10] <temporal_> AlexLehm we could configure the vertx-stack javadoc to point to the official javadoc online which would improve our docs

[19:41:22] <AlexLehm> yes, sure, i mean if BadApe wants to take a look at the docs now, he can do that with the jdk docs

[19:47:44] * ChanServ sets mode: +o purplefox [20:28:46] * ChanServ sets mode: +o purplefox

[21:01:14] <BadApe> hi sorry connection issues

[21:03:03] <BadApe> so i generated a key: keytool -genseckey -keystore keystore.jceks -storetype jceks -storepass secret -keyalg HMacSHA512 -keysize 2048 -alias HS512 -keypass secret, and got java.lang.RuntimeException: Algorithm not supported

[21:03:03] <BadApe> at io.vertx.ext.auth.jwt.impl.JWT.sign(

[21:03:03] <BadApe> at io.vertx.ext.auth.jwt.impl.JWTAuthProviderImpl.generateToken(

[21:04:14] <BadApe> temporal_, excuse my ignorance, but i assume you mean i need to log the issue here:

[21:04:44] <temporal_> yes

[21:05:08] <temporal_> just say that we could link to external javadoc like JDK javadoc (there may be others like Netty)

[21:18:18] <rbt> <pmlopes> @badape algorithm not supported means that the algorithm you're requesting is not present on your key ring, how are you signing? Did you specify hs512?

[21:18:39] <BadApe> thought i did

[21:19:18] <BadApe> is this not enough? keytool -genseckey -keystore keystore.jceks -storetype jceks -storepass secret -keyalg HMacSHA512 -keysize 2048 -alias HS512 -keypass secret

[21:20:51] <BadApe> HS256 seems to work, will use that for now

[21:23:11] <rbt> <pmlopes> That's how you generate a key ring but when signing you need to specify which alg to use, by default and according to the jwt spec if you do not specify one it should be hs256 and that's why it “works”

[21:24:32] <rbt> <pmlopes> So in the options you should pass alg=hs512

[21:25:42] <rbt> <pmlopes> Sorry options.setAlgorithm(“HS512”)

[21:27:42] <daum_> hi guys - i'm trying to build an app which has about ~5-6k concurrent connections, for a total thru put of about 150k reqs/sec. I'm also trying to query a database in my code. I know I should use the executeBlocking call. However right now whenever i start up the server, even just with the benchmark/hello world example, I just get a ton of connection reset by peer

[21:28:02] <daum_> was curious one what parameters /options i should be looking to tweak