Bypass concurrent login verification during mobile authentication.
Scenario:
When we have an active session in the web browser, we're unable to log in via mobile.
Fix:
We will skip the verification of concurrent login when the request is made through mobile.
Resolution:
The fix for the issue has been attached with this article. Check the "Jar Compatibility" section before downloading the fix jar file (.fjar file). Check this
link on how to apply the fjar file.

Jar Compatibility
Build No | File Name |
14820 | 14820_skipmobilesession.fjar |
New to ADSelfService Plus?
Related Articles
Security settings, Logo and other customisation for mobile app
Requirement: Security settings for mobile app is waiting for release in 14830 build version. In addition to this, server side support for separate logo for mobile app is currently under development. Meanwhile, customers are requesting customisations ...
CSRF login Issue
Issue: CSRF token mismatch during login. Trace: [07:01:21:901]|[10-05-2021]|[com.adventnet.servicedesk.authentication.internal.LoginUtil]|[INFO]|[69]: Invalid login CSRF token provided ::: sessionToken : null; cookieToken : ...
TFA : Failing Email Delivery of TFA Verification Code During Login
Issue: In a non-ESM setup with Graph configuration in the outgoing mail server settings, the sending of TFA verification codes via email fails when attempting to log in. Issue ID: SD-120339 Screenshot of Error: Trace of Error in Logs: ...
Query to show Technicians' login name, email, role and last login (PGSQL & MSSQL )
Tested in Build PGSQL (14300) or MSSQL (14306) SELECT AaaUser.FIRST_NAME "First Name", AaaUser.last_name "Last Name", adef.org_name "Account Name", sdo.name "Site Name", AaaContactInfo.EMAILID "E-mail", sduser.jobtitle, ar.name "Role", ...
Login | CAPTCHA is not shown | Account is not locked even after multiple tries (SD-121377)
Issue: The account is not locked when account lockout is configured and wrong password is entered multiple times Resolution: This is noted as issue SD-121377 and fixed in 14830. Kindly upgrade your application to 14830 or above. Workaround: If you ...