Thursday, September 13, 2018

Blue Prism ATA02 - Login Agent

Thought to write this post today to explain 'Login Agent' In Blue Prism. Since this is the very first thing that one should know while starting his/her preparation for Blue Prism exam or for any real world project.

So let's gets started!!!


INTRODUCTION:

In very general terms 'Login Agent' is nothing but a software. As any other software, this also has something to perform for us which is : It provides us a mechanism to login to an assigned windows device in a secure manner. So it really just a software and nothing else.

Blue Prism vendor deliver login agent with the installer of Blue Prism software. And it will be located in same installation media.

Another important point to remember is that any login agent supports only that version of Blue Prism application with which it will be delivered by Vendor. 

On the similar lines, Login Agent will support only those Operating systems which will be supported by Blue Prism application.

So in terms of compatibility, Login agent will behave the same way as Blue Prism Application will do with which Login agent had been delivered by vendor.


There are few prerequisites which we need to understand prior to installing Login Agent on any windows machines.

Below are these requirements:


  1. There should be Blue Prism Application installed on the machine where we would like to install Login Agent.
  2. There should be few security policies which system admin has to enforce on the windows machine so that Login Agent would work as expected.

First one in the above list is pretty straight forward. 
However, for the security policies , please refer below :

Any machine on which we need Login Agent to work properly, there should be few security policies enabled :

  1. The machine should not prompt for 'Ctrl+Alt+Del' while machine will come online after a reboot.
  2. There should not be any policy acceptance screen because there will be no one to accept those policies on the remote machine.
  3. System should not get locked after idle time.
These policies should be updated by System Administrator and can be updated by going in to Group and local system policies.

Finally, the user which will finally login to this machine, should have administrator level access.

Please note that the policies mentioned above are mandatory and Login Agent will not work as it should if not followed properly.

I hope this Introduction will help to understand the first few things for Login Agent.

In my next post, I will cover why we need a Login Agent and then afterwards we will cover 'How' a login agent would work.

Keep reading and if you find it helpful, please pass it along in your network.

2 comments: