TUI device registration/Authorization is failing

[dhanan-np]

1. OS: Unbuntu 20.04
2. Mysql db as a remote
3. Apache2 was already installed
4. installed using a user who is there in sudoer list. :

✓ jans             Generating smtp keys
✓ jre              Installing Jre
✓ jetty            Installing Jetty
✓ jython           Installing Jython
✓ rdbm-server      Importing ldif files to mysql
✓ apache2          Configuring apache2
✓ jans-auth        Generating OAuth openid keys
✓ jans-config-api  Deploying Jetty Service
✓ jans-fido2       Deploying Jetty Service
✓ jans-scim        Deploying Jetty Service
✓ jans-cli         Installing Jans Cli
✓ post-setup       Starting Jans Scim

now trying to run /opt/jans/jans-cli/config-cli-tui.py which is opening up the TUI and there I get a Prompt to authorize the device using a verification url like https://gluu.dummyhost/device-code?user_code=LBJR-KNBC

but when I am opening the url on browser, it first shows the Device Authorization window with continue button.
I click on it and it shows Error Encountered.
Backend logs I can see as -

2023-04-26 14:52:54,468 ERROR [qtp382750013-13] 353da04c-3e17-45c1-b11c-76896727ec6b [io.jans.as.server.service.SessionIdService] (SessionIdService.java:795) - Failed to get session by dn: jansId=a1e7a65f-fb5f-43bf-87d3-467fbe0e08cc,ou=sessions,o=jans. Failed to find entry: 'jansId=a1e7a65f-fb5f-43bf-87d3-467fbe0e08cc,ou=sessions,o=jans'
2023-04-26 15:09:10,461 INFO  [qtp382750013-18] 08239d2a-2541-4973-b6cf-8fdb3ef417ff [io.jans.as.server.auth.Authenticator] (Authenticator.java:301) - Authentication success for Client: '2000.5f6a12a6-ec0e-4868-af0d-8e98c27d1669'
2023-04-26 15:09:10,521 WARN  [qtp382750013-18] 08239d2a-2541-4973-b6cf-8fdb3ef417ff [io.jans.as.model.crypto.AbstractCryptoProvider] (AbstractCryptoProvider.java:254) -
WARNING! Key with alias: connect_1d7c3aaa-47b5-40ba-94d9-4281f1f13686_sig_rs256
        Expires In: 1 days
        Expires On: 2023-04-28 13:55:29
        Key Regeneration In: 2 days
        Today's Date: 2023-04-26 15:09:10
2023-04-26 15:09:10,675 INFO  [qtp382750013-16] 2b3de713-f78e-4cc8-afe2-1e61f073e53b [io.jans.as.server.auth.Authenticator] (Authenticator.java:301) - Authentication success for Client: '2000.5f6a12a6-ec0e-4868-af0d-8e98c27d1669'
2023-04-26 15:09:10,747 INFO  [qtp382750013-16] 2b3de713-f78e-4cc8-afe2-1e61f073e53b [as.server.authorize.ws.rs.DeviceAuthorizationRestWebServiceImpl] (DeviceAuthorizationRestWebServiceImpl.java:137) - Device authorization flow initiated, userCode: LBJR-KNBC, deviceCode: e0af13ffa1b3ab9c55afe09f951c60c7f4f1c33213b3f57d, clientId: 2000.5f6a12a6-ec0e-4868-af0d-8e98c27d1669, verificationUri: https://gluu.dummyhost/device-code, expiresIn: 1800, interval: 5
2023-04-26 15:10:11,334 INFO  [qtp382750013-18] 445591f1-9bf1-4084-9781-f911ca69bbc7 [as.server.authorize.ws.rs.DeviceAuthorizationAction] (DeviceAuthorizationAction.java:92) - Processing device authorization page request, userCode: LBJR-KNBC, code: null, sessionId: null, state: null, sessionState: null, error: null, errorDescription: null

[ossdhaval]

Looping in @devrimyatar and @manojs1978 for further comments.

[nynymike]

It should ask prompt you to login. Can you try this in incognito mode? Or clear the cookies for that domain... maybe there is something old?

[dhanan-np]

It should ask prompt you to login. Can you try this in incognito mode? Or clear the cookies for that domain... maybe there is something old?

I have already tried in incognito mode and different bowser also. Even I cleaned up and re-installed the application again, thinking of that there might be some problem with previous installation.

Do you think it is related to the user(which is not a root user but it is in sudoer list).
I have one more installation (where I am doing POC on Google Cloud) there also the user is not root but it is in sudoer list. And that is working.

[manojs1978]

yes might be issue with your user.
log will help.please share it.

between i followed below steps and created user and installed jans
but still not reproduced.

sudo adduser test
sudo usermod -aG sudo test
curl https://raw.githubusercontent.com/JanssenProject/jans/v1.0.13.nightly/jans-linux-setup/jans_setup/install.py > install.py

sudo python3 install.py

provided below details while installation

Do you acknowledge that use of the Janssen Server is under the Apache-2.0 license? [N|y] : y
Enter IP Address [...] :
Enter hostname [*************] : ************
Enter your city or locality : gggg
Enter your state or province two letter code : gg
Enter two letter Country Code : gg
Enter Organization Name : gggg
Enter email address for support at your organization : [email protected]
Enter maximum RAM for applications in MB [6630] :
Enter Password for Admin User [e0dwi%nxClS2] : Admin@123

after installation completion, launched
sudo /opt/jans/jans-cli/config-cli-tui.py

then followed device authentication url and added admin /Admin@123

[dhanan-np]

Please download the log files from here

[manojs1978]

did you tried again with shown above steps.?
is it resolved? if not please try once with above steps.

[dhanan-np]

Hello @manojs1978 , I tried but no success.
still getting this error-

2023-05-16 17:21:21,864 ERROR [qtp1226020905-18] f451c483-381b-4aee-b286-3baece8bc5bc [io.jans.as.server.service.SessionIdService] (SessionIdService.java:795) - Failed to get session by dn: jansId=209e3412-2e7f-471d-97cf-6c55640c412b,ou=sessions,o=jans. Failed to find entry: 'jansId=209e3412-2e7f-471d-97cf-6c55640c412b,ou=sessions,o=jans'

If you wish we can connect over call so that I can show you.
I am IST time

[ossdhaval]

@dhanan-np I just checked the same steps with latest Jans build and on Ubuntu 22. I could complete device auth successfully and access TUI. Same result when @manojs1978 tried on Ubuntu 20.

Is this still a problem at your end?

This is not reproducible and we should wait and see if any other community member reports the same behavior. Meanwhile, we should close this discussion and reopen it if the issue is reported again.

[dhanan-np]

Hello Mr. @ossdhaval , can we connect to check it live. May be we can draw some conclusion on it. I know it might not look worthy to you to check any issue if it is hampering one member, but for me it is like a barrier on moving towards Production.

[ossdhaval]

Closing this discussion since it is inactive for long time.