V6.1 - Why is there a Runtime Resource User Role?

[SteveBoomer]

Hi All, We are running v5.024 in one environment and have a DEV / Test environment running V6.1 (soon to be Production too). In v6.1 there is a new User Role called Runtime Resource which was not available out of the box in v5. It appears to have very limited permissions. I've searched through the Help Files that come with the installation, I've looked in the Installing Enterprise Edition 1 Rev1.0 PDF and I cannot find any mention of it. Is this role to be applied to the AD accounts used to log the Runtime Resource onto the domain? (stored in Credential Manager as Windows Login) Is this a testing role to see how the Runtime Resource will behave in Dev/Test before being released into Production? Or something completely different? Thanks in advance. Steve

[Armando_Antonio]

In the latest 5.x versions the role was added. Why? Because the runtime machines are usually defined as public entities when running by commands. And what is the problem with that? Well, it is basically when your process needs to use credentials because you will define the credential in the crendential manager and you had to define among other things a role that is going to have access to it. So the public runtime has a ""kind of anonimous"" role. Previously you had to select all roles otherwise the runtime machine will not have access using any of the other roles. So it is here in where the new runtime role comes to play. It a way to define that the runtime machine has permission to access a specific credential based on its role....... Hope it makes sense

[SteveBoomer]

Thanks for the reply Armando, much appreciated. So in an SSO environment, the domain accounts for the credentials need to be in an AD group that is allocated to the Runtime Resource role in Blue Prism? Regards, Steve

[Armando_Antonio]

I am sorry, I have not experienced anything with Active Directory myself yet, but what you say sounds like the way to go. As you can see, this new role has, I would say, the minimun permissions to just access BP, which is right. Now, an easy way to test that is to create a simple Process that get a crendential with that role and check if you got any exceptions there/or the expected behavior. (Trial and error). Or maybe some in the forum has the answer for your question.