Callbackparams
Author: h | 2025-04-24
CallbackParams Offers Elegant Parameterization for JUnit. CallbackParams is a JUnit add-on for parameterized testing. Download callbackparams-1.0-beta-3-sources.jar. callbackparams/callbackparams-1.0-beta-3-sources.jar.zip( 122 k) The download jar file contains the following class
CallbackParams - Browse /callbackparams-1.0-beta-3 at
Hi folks (cc @panva @svvac @madarche @sawyerh)Is that correct to assume that the same openIdClient instance should be handling both openIdClient.authorizationUrl() and openIdClient.callbackParams() for a particular authentication request.As I found out, it could be wrong, that if the instance is different between these 2 calls, then "callbackParams of undefined" and "state mismatch" errors could happen, especially in a multi-instance environment. You must be logged in to vote As far as I know the library does not hold state regarding the authentication flow.As long as you properly sync request state (e.g. nonce, state, code_challenge, etc.) between your instances, it should work provided that they share the same config. You must be logged in to vote 0 replies You must be logged in to vote 3 replies I can do no such thing without error stacktraces and reproduction repository/steps. The stated reason in your SO answer sounds wrong to me. You do not need to share an instance between the two steps to make PKCE work. You still need some state sharing mechanism for the checks to work, but this applies whether or not you end up using the same instance or not.Here is a toy implementation that uses two different servers (ports) and single-use Client instances that use a shared encrypted cookie to sync state (code verifier + nonce). @svvac you are right, I think the problem is with the caller, in my case it is XeroClient, it doesn't initialise the openIdClient for callbacks properly.I have raised a PR for themXeroAPI/xero-node#545 -->
CallbackParams - Browse /callbackparams-1.0-beta-5 at
CallbackParams - Browse /callbackparams-1.0-beta-6 at
. CallbackParams Offers Elegant Parameterization for JUnit. CallbackParams is a JUnit add-on for parameterized testing.Download callbackparams-1.0-beta-3.jar (CallbackParams)
CallbackParams - FREE Download CallbackParams 1.0.beta.4
Download callbackparams-1.0-beta-4.jar : callbackparams c
Download callbackparams-1.0-beta-6.jar : callbackparams c
. CallbackParams Offers Elegant Parameterization for JUnit. CallbackParams is a JUnit add-on for parameterized testing. Download callbackparams-1.0-beta-3-sources.jar. callbackparams/callbackparams-1.0-beta-3-sources.jar.zip( 122 k) The download jar file contains the following class
Download callbackparams-1.0-beta-2.jar : callbackparams c
Download callbackparams-1.0-beta-1.jar : callbackparams c
. CallbackParams Offers Elegant Parameterization for JUnit. CallbackParams is a JUnit add-on for parameterized testing. Download callbackparams-1.0-beta-3-sources.jar. callbackparams/callbackparams-1.0-beta-3-sources.jar.zip( 122 k) The download jar file contains the following classDownload callbackparams-1.0-beta-5.jar : callbackparams c
Comments
Hi folks (cc @panva @svvac @madarche @sawyerh)Is that correct to assume that the same openIdClient instance should be handling both openIdClient.authorizationUrl() and openIdClient.callbackParams() for a particular authentication request.As I found out, it could be wrong, that if the instance is different between these 2 calls, then "callbackParams of undefined" and "state mismatch" errors could happen, especially in a multi-instance environment. You must be logged in to vote As far as I know the library does not hold state regarding the authentication flow.As long as you properly sync request state (e.g. nonce, state, code_challenge, etc.) between your instances, it should work provided that they share the same config. You must be logged in to vote 0 replies You must be logged in to vote 3 replies I can do no such thing without error stacktraces and reproduction repository/steps. The stated reason in your SO answer sounds wrong to me. You do not need to share an instance between the two steps to make PKCE work. You still need some state sharing mechanism for the checks to work, but this applies whether or not you end up using the same instance or not.Here is a toy implementation that uses two different servers (ports) and single-use Client instances that use a shared encrypted cookie to sync state (code verifier + nonce). @svvac you are right, I think the problem is with the caller, in my case it is XeroClient, it doesn't initialise the openIdClient for callbacks properly.I have raised a PR for themXeroAPI/xero-node#545 -->
2025-04-03