By: Max Anderson Account Admin 25 Sep 2017 at 12:58 p.m. CDT

3 Responses
Max Anderson gravatar
Currently I'm going through the SSO process and, I'm getting to a page that just stops the process all together. [Page when stopped](https://photos.app.goo.gl/BQoRci7pSnb8z7t22) here is my configuration: [OpenId Config](https://photos.app.goo.gl/i3zlOFNhYeDmjplB3) I did move from localhost to my internal IP to see if it made a difference but it didn't. I had this working before with 3.0.1, but 3.1.0 seems to have something different that I'm not setting up correctly.

By Aliaksandr Samuseu staff 25 Sep 2017 at 5:33 p.m. CDT

Aliaksandr Samuseu gravatar
Hi, Max. Could you provide a more straightforward reproduction steps for this issue? It's hard to say what leads to it. Do you create client registration manually, or register dynamically with some RP? Do you use any custom auth scripts? From your first screenshot I can't tell what url this page belongs to; url as well may contain a useful error codes in it. Please do a more thorough investigation and gather more clues for us to evaluate. You could use SAMLTracer (or similar) browser plugin to capture at least what happens in the frontchannel communications, then share with us. Check [logs docs page](https://gluu.org/docs/ce/3.1.0/operation/logs/), and search related logs for errors.

By Max Anderson Account Admin 26 Sep 2017 at 9:34 a.m. CDT

Max Anderson gravatar
I'm using OpenID Connect, I created the registration (OpenID config from the screen shot) manually. I'm using spring boot, the same client use to work with Gluu 3.0.1, but now I'm trying 3.1.0 it doesn't work like it use to. It seems to me like a config issue that I'm missing. Here is my config from my Spring Boot app: ``` security: oauth2: client: clientId: "@!91C9.0534.D806.A1BB!0001!CD22.9B15!0008!85FE.875A.051F.4445" clientSecret: secret accessTokenUri: https://mydomain/oxauth/token userAuthorizationUri: https://mydomain/oxauth/authorize clientAuthenticationScheme: form scope: profile email tokenName: access_token authenticationScheme: form resource: userInfoUri: https://mydomain/oxauth/userinfo server: port: 8443 ssl: enabled: true key-alias: tomcat key-store: "keystore.p12" key-store-type: PKCS12 key-store-password: changeit key-password: changeit logging: level: root: DEBUG ``` Here is the full url: ``` https://mydomain/oxauth/login?response_type=code&client_id=@!91C9.0534.D806.A1BB!0001!CD22.9B15!0008!85FE.875A.051F.4445&scope=profile%20email&state=r0oFTr&redirect_uri=https://10.170.158.190:8443/login ``` This url happens after I login. It just stays there. Checking the main log that I usually check for issue oxauth.log it seems it was successful: ``` 2017-09-26 14:30:24,556 INFO [qtp2008017533-12] [org.xdi.oxauth.service.AuthenticationService] (AuthenticationService.java:515) - Attempting to redirect user: User: org.xdi.oxauth.model.common.User@76588c6 2017-09-26 14:30:24,558 INFO [qtp2008017533-12] [org.xdi.oxauth.auth.Authenticator] (Authenticator.java:342) - Authentication success for User: 'max.anderson' ```

By Aliaksandr Samuseu staff 19 Oct 2017 at 10:56 a.m. CDT

Aliaksandr Samuseu gravatar
Hi, Max. Do you still keep experiencing this issue? Please note that Gluu CE 3.1.1 has been released and you may opt to try your flow in the newer version as whatever causes it could be fixed there. Regarding data provided by you before (sorry for the late response), a couple of thoughts: 1. `scope=profile%20email` - you're missing `openid` scope in your authz request which is mandatory by OIDC spec, and oxAuth isn't guaranteed to behave predictably if it's omitted. 2. Judging by screenshot of your client's metadata, you don't specify neither `response_type`, nor `grant_type` explicitly in it, and I would strongly recommend to specify it. Judging by your authz request url from above, I would recommend to use `code` and `authorization_code`, correspondingly