Users & Roles in Lifetime

Hi João,

The security mode with LifeTime is a bit different than the old one.
That is one of the changes. A developer can list all applications if it has access to the environment.

There were multiple reasons for that change.
The main reason is that when planning stagings of an application, users need to have context about the dependencies.
Even if they can't change them, they can still plan a deployment to be approved later.
If there were applications that he could not see, then it would be impossible. And we couldn't even give any "fix" suggestions because for that user those applications would not exist.

There is also the situation where you have reusable components on your server.
They are there to make life usefull for the developers (and to reduce maintenance costs).
But since developers don't see it, they can't ask anyone for permissions (or to refactor some eSpace/extension into a shared component). So he will code it once again.

(There are more reasons that I can remember, but I guess those are the 2 most important ones)

Regards,
João Rosado

Hi,

Will that webinar become available somewhere? This was always done with other webinars, couldn't join that day :-(.

Kind regards,
Evert

 
 Hi Evert,

I believe it will be available soon, as usual with other webinars.

Regards,
João

1. I'd like to set up a role for a lead developer that has configure infrastructure access for the DEV environment but not for QA and PROD, Lifetime currently limite configure infrastructure only to be set for all environments.  We need a role that has more access than change and deploy to DEV but not to PROD, is there any way around this limitation?
2. Roles cannot be granted application specific levels, only uses.  THis goes agains our role bsed access security standards.  IS there any work arund for this limimtation? 

 

Hi Gary,

Regarding the first question I think you misunderstood lifetime permission levels. The Configure Infrastructure permission is cross environment and a Role with that permission gives the ability to configure users on lifetime. If you want a user to be able to configure an environment (environment settings, database connections, zones, etc.) you have to set the its Role permission level for that environment to 'Full control'.

Regarding the second question, currently you have to setup application specific levels for each user.

Regards

Thanks João,

Your correct I think I misstated my concern on the full control, that is the setting to do what I need.

Are there any thoughts to setting application access levels to a role in addition to a user?