By: matt dillenkoffer user 31 Jul 2016 at 7:07 p.m. CDT

1 Response
matt dillenkoffer gravatar
I have a redirect uri that has to have a lot of request parameters in it for the request to go where I want when it comes back from gluu with the auth_code in it. No matter how I encode the uri when calling the authorize endpoint gluu keeps telling me they don't match. My question is how would I debug this, it'd be nice it the logs would say value a doesn't match value b and show me what it's comparing. But even if I can't debug it what's the expectation? Should I just put the original url through a url encoder and send that as the redirect_uri value and put the non encoded uri in the gluu client setup or should I put the encoded uri value in both places? /oxauth/seam/resource/restv1/oxauth/authorize?redirect_uri=http://my.server?requiredParameter=245 needs to be /oxauth/seam/resource/restv1/oxauth/authorize?redirect_uri=http%3A%2F%2Fmy%2Eserver%3FrequiredParameter%3D245 what do i put in the Gluu config encoded or not encoded?

By matt dillenkoffer user 31 Jul 2016 at 10:01 p.m. CDT

matt dillenkoffer gravatar
Nevermind I must have fat fingered something, I send it to gluu as request parameter url encoded and put the value in gluu client as non-url encoded and it seems to work fine.