Hash return in request_url instead of ?

By: Eric Alter user 23 Feb 2017 at 1:56 p.m. CST

2 Responses
Eric Alter gravatar
When url requested with hash, the query parameters dont go back to application or processing server. need to have mechanism for proving ? instead of # As mention in this ticket: https://support.gluu.org/other/1112/why-idp-connect-callback-pass-instead-of/ We have the same issue, see Response Header below: Access-Control-Allow-Origin:* Connection:close Content-Length:0 Date:Thu, 23 Feb 2017 19:46:58 GMT Location:https://local.servicesenligne:3333/authorize?**#**session_state=d8262c7c-6eff-4edd-9ece-c6d3269c60e4&scope=user_name+email+openid+uma_authorization+profile&state=B5puHoyF0pXN0grfWsfOcfFze1CqcRSOmMKr83RI&expires_in=3599&token_type=bearer&id_token=eyJraWQiOiIxZGU0OWY4Ni0xMTVlLTQ0OWYtODM5MC1kN2QwMzU5NDlmNmYiLCJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJpc3MiOiJodHRwczovL2xhYmx3czAyYS5pbGUubW9udHJlYWwucWMuY2EiLCJhdWQiOiJAITUwRjcuMDJBQy4yNUI2LkU1ODUhMDAwMSFCOTQxLkJDMTIhMDAwOCEzRjRGLjIzNkMiLCJleHAiOjE0ODc4ODI4MTgsImlhdCI6MTQ4Nzg3OTIxOCwibm9uY2UiOiJCNXB1SG95RjBwWE4wZ3JmV3NmT2NmRnplMUNxY1JTT21NS3I4M1JJIiwiYXV0aF90aW1lIjoxNDg3ODc5MjE3LCJhdF9oYXNoIjoiTVdCT1JhakNFejVyYlplTDE3XzdOZyIsIm94VmFsaWRhdGlvblVSSSI6Imh0dHBzOi8vbGFibHdzMDJhLmlsZS5tb250cmVhbC5xYy5jYS9veGF1dGgvb3BpZnJhbWUiLCJveE9wZW5JRENvbm5lY3RWZXJzaW9uIjoib3BlbmlkY29ubmVjdC0xLjAiLCJ1c2VyX25hbWUiOiJhZ2x1dSIsImVtYWlsIjoibGhvZ3VlQHZpbGxlLm1vbnRyZWFsLnFjLmNhIiwiaW51bSI6IkAhNTBGNy4wMkFDLjI1QjYuRTU4NSEwMDAxIUI5NDEuQkMxMiEwMDAwITg1M0QuNTA5MSIsIm5hbWUiOiJHbHVlIFBvcnRhaWwiLCJmYW1pbHlfbmFtZSI6IlBvcnRhaWwiLCJnaXZlbl9uYW1lIjoiR2x1ZSIsInN1YiI6IkAhNTBGNy4wMkFDLjI1QjYuRTU4NSEwMDAxIUI5NDEuQkMxMiEwMDAwITg1M0QuNTA5MSJ9.QFePZp04wzPIMLPtC9Py7gOB4NAU__sTJo_Op2wp_YbXmkj-H0Txxmnu0w7SZg1-ki5eGKcC5qrwPaMW5mt7NaIblTsugpay7c0Hr22J14ta9sOBPGAmePrfnYFAVM15qZAi-UrEZeRnkK1vFiJSAKPNz20jCUjclTbkf-hKBjo3S837XTMbfAQRgEFJ00jPbtxQz_jtHk-3vSEcngwbdSCMTDiMwtQ4IhX7w8iOShojz3j23gqkUuo6Pc4zpBaVDrL871TdQCXPiigmSdkMQqL-E8466D-uZ8sCgMAZrUfj7yHvcMwNj55hIUfEPV6FP4JHfliFaoYZbCt9NRUOKg&access_token=b372cfee-4dfe-4f27-8af5-01c23d60c483 Server:Apache Could you please provide us some information to solve this issue, Can we set this on configuration? Thank you, Eric
Rhel72
closed

Answers

By Michael Schwartz Account Admin 27 Feb 2017 at 11:06 p.m. CST

Copy
Michael Schwartz gravatar
Javier, can you comment or ask questions about this issue?

By Javier Rojas staff 01 Mar 2017 at 1:19 p.m. CST

Copy
Javier Rojas gravatar
Hello Eric, Since response parameters are returned in the Redirection URI fragment value, the Client needs to have the User Agent parse the fragment encoded values and pass them to on to the Client's processing logic for consumption. http://openid.net/specs/openid-connect-core-1_0.html#FragmentNotes Also, you can specify the response_mode param in the authorization request: query, fragment or form_post http://openid.net/specs/oauth-v2-multiple-response-types-1_0.html#ResponseModes http://openid.net/specs/oauth-v2-form-post-response-mode-1_0.html#FormPostResponseMode Please check the following tests for response_mode param: https://github.com/GluuFederation/oxAuth/blob/master/Client/src/test/java/org/xdi/oxauth/ws/rs/AuthorizationResponseModeHttpTest.java Regards Javier

Post an answer