Improvement #12128
closed
QR code generator for both OAUTH and MSSL agents
Added by Arshana Atapattu 5 months ago.
Updated about 17 hours ago.
Description
Currently the generated QR code can only used for MSSL agents.
Need a mechanism to generate QR code for OAUTH as well.
This could be a tenant wise configuration or server wise configuration.
Files
- Assignee set to Sathira Perera
- Project changed from Backlog to product-uem 7.0.0 GA
- Status changed from New to Needs Improvement
- % Done changed from 0 to 80
- Due date set to 04/11/2024
- % Done changed from 80 to 100
- Status changed from Needs Improvement to QA
- Project changed from product-uem 7.0.0 GA to product-uem 6.4.0 GA
Can't generate QR code without enabling MSSL.
!/home/sapna/Downloads/Screenshot from 2025-02-07 15-30-01.png
!
Error log:
TID: [2] [api/device-mgt/android/v1.0] [2025-02-07 09:58:44,354] ERROR {io.entgra.proprietary.uem.platform.android.core.impl.AndroidCommonServiceImpl} - Couldn't get a access token for user arshana
!/home/sapna/Downloads/Screenshot from 2025-02-07 15-29-03.png
!
- Status changed from QA Reject to QA
- Status changed from QA to QA Reject
QR code is generating.
token expiry time is not changing in the Oauth method.
this will be handled with this https://roadmap.entgra.net/issues/12780
Butt when try enroll a device, device does not enroll.
Device enrollment is stuck in the authenticating window in the device.
Error log from logcat in the device: [3]
[3]
2025-03-26 12:22:07.968 17984-21411 Volley pid-17984 E [1877] NetworkUtility.shouldRetryException: Unexpected response code 400 for https://uem.gw.entgra.net:443/token
- Status changed from QA Reject to QA
- Status changed from QA to QA Accept
was able to enroll a device into super tenant with the OAuth agent
- Status changed from QA Accept to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by