Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

LDAP authentication

MU, CQR, PQRS, etc.

Last Post by Anonymous 1 second ago

4 Posts

3 Users

0 Reactions

55 Views

RSS

ronmoses

(@ronmoses)

Posts: 158

Estimable Member

Topic starter

We're having what appears to be an intermittent problem with CQR. Sometimes it uploads fine, but we're getting very frequent errors. GE's engineers have told us it's an LDAP authentication problem. I have only the vaguest of ideas what that means (it relates to Active Directory, I believe). They've also told us it's not their problem and we're more or less on our own with this one. We're at a loss to understand why LDAP authentication would work some times and not others, so we're wondering if anyone else has had to struggle with this?

The errors in QIE start like this:

CustomReceiver error (consecutive errors=2): javax.script.ScriptException: sun.org.mozilla.javascript.internal.WrappedException: Wrapped com.qvera.qie.exception.NoResultsException: Error calling Web Service 'Common Event Model': java.lang.Exception: Http Status: 500 Internal Server Error

The JBOSS console errors look like this:

[EXCEPTIONID: CENEMRAPP31430156392262] An unexpected exception occured while authenticating user.
org.springframework.security.authentication.AuthenticationServiceException: An error occured during LDAP authentication.

Posted : May 6, 2015 1:37 am

Luladin

(@luladin)

Posts: 25

Eminent Member

Is the server that is specified in ServerSetup to handle the LDAP requests set on a reboot schedule? Just curious if it's possibly down when the job is attempting to run which isn't allowing it to authenticate the user. If it isn't it then it might be beneficial to review the security log on the server specified to see if there are failed authentication attempts and if it's even making it to that point when it tries to authenticate.

We've had issues with special characters in the password field for the account used (%, #, $, symbols like that) but I don't think that would explain the intermittent issues you are seeing so likely isn't that.

-Jon

Posted : May 6, 2015 2:40 am

bruins1986

(@bruins1986)

Posts: 233

Reputable Member

As above: do you happen to run a nightly JBoss reboot? The common event model calls out to the jboss. Or does the schedule you follow mirror those errors in anyway?

Posted : May 6, 2015 10:17 am

ronmoses

(@ronmoses)

Posts: 158

Estimable Member

Topic starter

We do not do a nightly reboot. We do a monthly downtime where we shut down those services first.

Posted : May 7, 2015 3:55 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
1 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0