By: Dominique Petitpierre user 12 Mar 2018 at 10 a.m. CDT

5 Responses
Dominique Petitpierre gravatar
Hello, in the test client oxauth-rp of gluu 3.1.2, when one submits the form ```Authorization Endpoint``` requesting a ```CODE``` Response Type, then the generated code is not automatically filled in the ```Code``` input field of the ```Token Endpoint``` section. - Is there a way to fix that? This was working in version 3.0.1; Also other fields are correctly filled in (e.g. the ```Access Token``` input field of the section ```User Info Endpoint```). This is quite annoying as the default validity duration of the code is 60 seconds and obtaining it manually through other means is cumbersome. In case it matters I have tested with Firefox 58 and Chromium 64 on Linux. Also this section ```Authorization Endpoint``` is not followed like the others by a "Code Request" and "Code Response": it looks like it was overlooked. In this case it would have been useful in order to copy manually the code from the response. - Could you add these authorization code request and response sections in a future version of oxauth-rp? Thanks in advance for your answers!

By Thomas Gasmyr Mougang staff 12 Mar 2018 at 11:06 a.m. CDT

Thomas Gasmyr Mougang gravatar
Hi Dominique, We are about to reproduce your issue. Can you provide the link you have followed and other information you think may help? Thanks

By Dominique Petitpierre user 12 Mar 2018 at 11:37 a.m. CDT

Dominique Petitpierre gravatar
Hello, I did not follow any link: I just used a locally installed gluu 3.1.2 distribution with oxauth-rp enabled (https://server/oxauth-rp/home.htm). As mentioned in my first post,the problem does not occur in my 3.0.1 installation. It seems to me that the embedded javascript at the end of the ```oxauth-rp/home.htm``` HTML page (just before the ```<div class="footer">``` element) does not behave the same. (It's just a guess: I am not a javascript programmer.)

By Thomas Gasmyr Mougang staff 13 Mar 2018 at 4:01 a.m. CDT

Thomas Gasmyr Mougang gravatar
Hi Dominique, > Is there a way to fix that? **Yes** > How? **Replace the page `home.xhtml` from `opt/gluu/jetty/oxauth-rp/webapps/oxauth-rp.war` with the one provide as attachment on this post.** Steps to do that. 1. Log into gluu container 1. cd into `opt/gluu/jetty/oxauth-rp/webapps/` 1. copy the provide `home.xhtml` page in the current directory 1. Run the command `zip -u oxauth-rp.war home.xhtml` 1. Stop and start the `oxauth-rp` service With that change the code field will be populated automatically. Hope that help. Thanks.

By Dominique Petitpierre user 13 Mar 2018 at 7:16 a.m. CDT

Dominique Petitpierre gravatar
Hi Thomas, it works: the ```Code``` field is populated! Thanks for the fix! I maintain my request for enhancement; it would be useful for a newbie to see the HTTP exchange related to the ```Authorization Endpoint``` form: > Also this section Authorization Endpoint is not followed like the others by a "Code Request" and "Code Response": it looks like it was overlooked. In this case it would have been useful in order to copy manually the code from the response. > > - Could you add these authorization code request and response sections in a future version of oxauth-rp? Thanks again for your help!

By William Lowe user 13 Mar 2018 at 11:56 a.m. CDT

William Lowe gravatar
Thanks, Dominique! [Updated code added](https://github.com/GluuFederation/oxAuth/pull/766) and will be resolved in Gluu 3.1.2. Thanks again! Will