Users get frustrated when having to remember to enter domain\ prior to the username when logging into ESS. I believe only one domain is allowed with ESS, why not set that as a default so that the user does not have to enter when logging in.
We use SAML, OAuth2 for many programs in our environment. Many of our products allow for an active directory integration using NTLM and LDAP and our users have no issues.
I recent review of our helpdesk tickets found that the most frequent issue of users reaching out to the IT Helpdesk was logging into Sage HRMS's Employee Self Service. The login to ESS is the only credential/username that requires a user to include our AD domain identifier (@domain.com or domain/username) as a part of the login process.
We've been using Sage X3 and Sage HRMS for many years and use a lot of other products from the Sage ecosystem too. This issue is frustrating to support, impacts the HR and IT departments and creates challenges to provide a good experience for our users.
I am grateful that Sage does include an MFA option with the LDAP connection to AD now, and hope that continues when they choose to prioritize resolving the complicated login that exists now.
We use SAML, OAuth2 for many programs in our environment. Many of our products allow for an active directory integration using NTLM and LDAP and our users have no issues.
I recent review of our helpdesk tickets found that the most frequent issue of users reaching out to the IT Helpdesk was logging into Sage HRMS's Employee Self Service. The login to ESS is the only credential/username that requires a user to include our AD domain identifier (@domain.com or domain/username) as a part of the login process.
We've been using Sage X3 and Sage HRMS for many years and use a lot of other products from the Sage ecosystem too. This issue is frustrating to support, impacts the HR and IT departments and creates challenges to provide a good experience for our users.
I am grateful that Sage does include an MFA option with the LDAP connection to AD now, and hope that continues when they choose to prioritize resolving the complicated login that exists now.
Thank you for your feedback. This will be forwarded to the product team for review and consideration in an upcoming release.