Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Current »

FlexDeploy provides its own proprietary repository for managing security, including users, groups, and permissions. The implementation provides a fine-grained permission model so that groups can be configured to match the roles and responsibilities of any organization. FlexDeploy also supports LDAP and Active Directory integration for user authentication.

Security administration is restricted to FlexDeploy Administrators only.

Security Administration

See authentication and authorization summary details below for quick reference.

Authentication

You can configure users in FlexDeploy internal realm or use external LDAP server.

  • See Users to maintain users in FlexDeploy internal realm. If you use this option then you are not relying on external directory servers.
  • You can use Active Directory or other LDAP server for authentication and authorization, see Realms for reference. FlexDeploy user record will still be created when user from external LDAP server logs in for first time. See new user process on Realms page.
  • You can also use both internal as well external realm for users. Users will be first authenticated against external realms and if not successful internal realm will be used.

Authorization

In order to control access to various parts of FlexDeploy, you will be configuring permissions for FlexDeploy groups. FlexDeploy supports coarse and finer grained permissions, see below for details.

Permissions are mainly controlled using FlexDeploy Groups even when using external realm. When using external realm, you can map external directory groups to FlexDeploy groups. Group mapping allows for less security maintenance when new users start using FlexDeploy.

  • Use global permissions control access to various objects in FlexDeploy. Global permissions do not control access at individual item level but rather at entire object level, i.e. if you grant Create / Update access for Workflow to group, members of that group can create or update any workflow. See global permissions for FlexDeploy group.
  • Use deployment permissions to restrict available environments on deployment request form. See deployment permissions for FlexDeploy group. For example, if you want to restrict specific group of users from deploying environments other than development and test, then configure deployment permissions accordingly. Alternatively, you can allow for deployment to all environments and setup approvals using FlexDeploy approvals or external change management system approvals.
  • Finer grained permissions
    1. Project - control access (read, create, configure, execute etc.) to specific projects for FlexDeploy groups. You can configure this for a project or folder. Configurations at folder level apply to all projects contained in it. See Project Security. This model allows for restricting configuration edits of projects to specific groups and still allow others to view and execute build / deploy on projects.
    2. Release - control access (read, configure, execute etc.) to specific release for FlexDeploy groups. You can configure this using global permissions and override at specific release as necessary. See Release Security.
    3. Pipeline - control access (abort, replay, skip etc.) on pipeline execution. Pipeline allows for abstraction in to roles that are mapped to FlexDeploy group and/or users. For example, developers, leaders, managers, operators etc. are some examples of pipeline roles. You can define permissions on each pipeline role. See Pipeline team security.

Permission Matrix

Object TypePermissionNotes
Project1 ReadProject read is allowed, i.e. project can be opened by user.
Project1 View LogsProject execution and associated logs can be viewed. 
Project1 Create Folder/Application/ProjectProject, folder, application can be created.
Project1 Configure Folder/Application/ProjectProject, folder, application can be configured.
Project1 Configure FilesProject files can be populated and updated.
Project1 Configure CommandsDeployment commands (EBS) can be updated. This should be restricted to admin users.
Project1 ExecuteProject build/deploy/test request can be submitted. Deployment environments are further controlled by Deployment Permissions.
Project Page ViewAllows access to Project menu.
Approval Setup ReadApprovals (outside of pipeline) can be read.
Approval Setup Create / UpdateApprovals (outside of pipeline) can be created or updated.
Window Setup ReadSchedule windows (outside of pipeline) can be read.
Window Setup Create / UpdateSchedule windows (outside of pipeline) can be created or updated.
Notification Setup ReadConfigured notifications (email) can be read.
Notification Setup Create / UpdateAdditional notifications (email) can be created or updated.
Notification Setup DeleteAdditional notifications (email) can be deleted.
Workflow ReadWorkflow (build,deploy, test etc.) can be read. This contains execution code for build and deployment.
Workflow Create / UpdateWorkflow (build,deploy, test etc.) can be created or updated. This contains execution code for build and deployment.
Release2 ReadRelease (collection of projects for specific delivery) can be read.
Release2 Create/UpdateRelease (collection of projects for specific delivery) can be created or updated.
Release2 Create SnapshotCreate snapshot is process of including build version in to release. Developer can be responsible for this as well.
Release2 Configure Project ListProjects and packages can be added or removed from release. 
Release2 Configure PipelinePipeline can be configured on release with this permission.
Release2 Configure CMSChange management system details can be configured on release with this permission.
Release2 Manage LifecycleRelease start, pause, end actions are allowed with this permission.
Release2 Grant PermissionsRelease permission can be changed with this permission, otherwise Administrator users can configure permissions.
Pipeline ReadPipeline can be read. Pipeline defined promotion process through various environments.
Pipeline UpdatePipeline can be created or updated.
Report ReadReports can be read.
Environment Instance ReadTopology object read permission.
Environment Instance Create / UpdateTopology object update permission. Allows update to properties like folder, user, password etc. 
Environment ReadTopology object read permission.
Environment Create / UpdateTopology environment can be created or updated.
Instance ReadTopology object read permission.
Instance Create / UpdateDeployment target (logical) can be created or updated.
Endpoint ReadEndpoint (SSH configuration) to connect to target nodes can be read.
Endpoint UpdateEndpoint (SSH configuration) to connect to target nodes can be created or updated.
Scheduled Task ReadScheduled task (deployment outside of pipeline waiting for schedule) can be read.
Scheduled Task UpdateScheduled task (deployment outside of pipeline waiting for schedule) can be overriden, allows immediate run of deployment.
Plugin ReadPlugin details can be read.
Plugin UploadPlugin can be uploaded and activated. Generally restricted to Administrators. 
Property Set ReadConfigured property details (plugin or workflow based) can be read. Internal details.
Template ReadTemplates can be read. Templates allow creation of projects using CSV input data.
Template Create / UpdateTemplates can created or updated.
Defaults ReadDefaults can be read. Defaults allow some customizable defaults when new objects are created in FlexDeploy.
Defaults UpdateDefaults configuration can be updated.
FlexField ReadFlexField configurations can be read. FlexFields are custom inputs to build and deploy workflow requests.
FlexField UpdateFlexFields can be configured (enalbed)
Test Type ReadTest type names can be read. 
Test Type Create / UpdateTest type names can be created or updated.
Object Type ReadObject Type customization details can be read. Customization is restricted to Administrator users.
Testing Tool ReadTesting tools configurations can be read. 
Testing Tool Create / UpdateCutom testing tools configurations can be created or updated.
Issue Tracking System ReadIssue tracking system configurations can be read.
Issue Tracking System UpdateGlobal configurations for Issue Tracking Systems can be updated.
Change Management System ReadChange management system configurations can be read.
Change Management System UpdateGlobal configurations for change management systems can be updated. 
Cloud Account ReadCloud Account details can be read.
Cloud Account Create / UpdateCloud Account can be created or updated.
Account Provider ReadAccount providers for cloud accounts can be read.
Account Provider Create / UpdateAccount providers (custom) for cloud accounts can be created or updated.
User ReadUser information can be read. Users management is restricted to Administrator users.
Group ReadGroup information can be read. Group management is restricted to Administrator users.
Realm ReadRealm information can be read. Realm configuration is restricted to Administrator users.
Credential ReadCredential details can be read. Note that secret text like password can never be read in clear text, hence you can only see details necessary to request credential from store.
Credential Create / UpdateCredential details including secret text like password can be be entered. 
Credential DeleteCredential can be deleted if not used.
Credential Store ReadCredential store details can be read. Management of stores is restricted for Administrators.
Credential Store Provider ReadCredential store providers can be read. Management of store providers is restricted for Administrators. 
Deployment Permissions
Allows control which environments user is allowed to perform deployment. 

1 - Project level permissions can be setup at individual project, folder or application (folder or application level setup will apply to child folder and projects unless overridden).

2 - Release level permissions can be setup for individual release.

  • No labels