sintax1 / lab-manager Goto Github PK

lab-manager currently passes credentials to vsphere-controller upon instantiation. vsphere-controller attempts to login to the vSphere Server using these credentials and may fail in various ways such as host unreachable, authentication failure, timeout, etc. When an authentication failure occurs an exception is thrown.

vsphere-controller is an eventemitter and lab-manager is not catching the exceptions using the .once('error', mechanism, so the app is crashing. As a workaround, lab-manager is catching all uncaught exceptions but this is bad.

Need to figure out a better way to catch/handle authentication failures.

The intent is that a user will login via web interface where the Angular auth/passport component passes the credentials and attempts to login with the vsphere-controller nodejs module. Upon, successful authentication, the user session token is created and stored to verify the users session through it's life. The vsphere-controller instance should be stored and reused only for that user, as it contains it's own session information between the lab-manager and vCenter Server.

When another user is to login, that user must get their own vsphere-controller instance and not share amongst other logged in users.

Need to research whether this is working as intended and is there a better way to store the vCenter session within the user's session?