Security
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. Additionally, you can also enable Single Sign-On and Multi Factor Authentication using external service or corporate security solution.
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 an LDAP server for authentication and authorization. See Realms for reference. A FlexDeploy user record will still be created when users from your external LDAP server login for the first time. See new user process on Realms page.
You can use both internal as well external realm for users. Users will be authenticated in the order defined on the Realms page.
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 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 to 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 more information.
Use deploy permissions to restrict available environments on deployment request form. See Deploy Permissions. 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
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.
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.
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.
Some object types allow permissions to be granted for an individual instance of the object, for instance, you can give permission to update the EBS target group to the EBS lead, but not allow them to modify other target groups.
Permission Matrix
Object Type | Permission | Notes | General Recommendation |
---|---|---|---|
Approval Setup | Â Read | Approvals (outside of pipeline) can be read. | All Users |
Approval Setup | Â Create / Update | Approvals (outside of pipeline) can be created and updated. | Change Management/Operations |
Credential | Read | Credential 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. | All Users |
Credential | Create / Update | Credential details including secret text like password can be be entered. | FD Administrators, DBA, Middleware Administrators |
Credential | Delete | Credential can be deleted if not used. | FD Administrators, DBA, Middleware Administrators |
Credential Store | Read | Credential store details can be read. Management of stores is restricted for Administrators. | All Users |
Credential Store Provider | Read | Credential store providers can be read. Management of store providers is restricted for Administrators. | All Users |
Defaults | Â Read | Defaults can be read. Defaults allow some customizable defaults when new objects are created in FlexDeploy. | All Users |
Defaults | Â Update | Defaults configuration can be updated. | FD Administrators |
Endpoint | Â Read | Endpoint (SSH configuration) to connect to target nodes can be read. | All Users |
Endpoint | Â Update | Endpoint (SSH configuration) to connect to target nodes can be created and updated. | FD Administrators |
Environment | Â Read | Topology object read permission. | All Users |
Environment | Â Create / Update | Topology environment can be created and updated. | FD Administrators |
File Type | Read | File Type details (Match script, default scripts, etc.) can be read. File Types apply to specific Package-based projects. | All Users |
File Type | Update | File Type details can be updated. | FD Administrators |
FlexField | Â Read | FlexField configurations can be read. FlexFields are custom inputs to build and deploy workflow requests. | All Users |
FlexField | Â Update | FlexFields can be configured (enabled) | FD Administrators |
Group | Read | Group information can be read. Group management is restricted to Administrator users. | All Users |
Integration Accounts | Â Read | Integration Accounts can be read. Integration Accounts are connection details for Source Repository, Change and Issue Management System, Cloud Providers, and more. | All Users |
Integration Accounts | Â Create / Update Delete | Integration Accounts can be created, updated, or deleted. | FD Administrators |
Integration Providers | Read | Integration Providers can be read. Integration Providers represent other DevOps tools useful in CI/CD process. | All Users |
Integration Providers | Â Create / Update Delete | Integration Providers can be created, updated, or deleted. | FD Administrators |
Notification Setup | Â Read | Configured notifications (email) can be read. | All Users |
Notification Setup | Â Create / Update | Additional notifications (email) can be created and updated. | All Users |
Notification Setup | Â Delete | Additional notifications (email) can be deleted. | All Users |
Notification Templates | Read | Notification Templates can be read | All Users |
Notification Templates | Create / Update | Custom Notification Templates can be created and updated | FD Administrators |
Pipeline | Â Read | Pipeline can be read. Pipeline defined promotion process through various environments. | All Users |
Pipeline | Â Update | Pipeline can be created or updated. | FD Administrators |
Plugin | Â Read | Plugin details can be read. | All Users |
Plugin |  Upload | Plugin can be uploaded and activated. Generally restricted to Administrators. | FD Administrators |
Realm | Read | Realm information can be read. Realm configuration is restricted to Administrator users. | All Users |
Release1 | Â Read | Release (collection of projects for specific delivery) can be read. Release permissions can be overridden for individual Releases as well. | All Users |
Release1 | Â Create/Update | Release (collection of projects for specific delivery) can be created and updated. | Change Management/Operations |
Release1 | Â Create Snapshot | Create snapshot is process of including build version in to release. Developer can be responsible for this as well. | Developers, Technical Leads |
Release1 |  Configure Project List | Projects and packages can be added or removed from release. | Developers, Technical Leads |
Release1 | Â Configure Pipeline | Pipeline can be configured on release with this permission. Access to Override members on Teams tab is also controlled by this permission. | Change Management/Operations |
Release1 | Â Manage Lifecycle | Release start, pause, end actions are allowed with this permission. | Change Management/Operations |
Release1 | Â Grant Permissions | Release permission can be changed with this permission, otherwise Administrator users can configure permissions. | FD Administrators |
Report | Â Read | Reports can be read. | All Users |
Resource Type | Â | Â | Â |
Scheduled Task | Â Read | Scheduled task (deployment outside of pipeline waiting for schedule) can be read. | All Users |
Scheduled Task | Â Update | Scheduled task (deployment outside of pipeline waiting for schedule) can be overridden, allows immediate run of deployment. | Change Management/Operations |
Scheduled Window Setup | Read | Schedule Windows (for Project execution) can be read. Schedule Windows are setup on Folder and applies to all projects under it, unless overridden in folder hierarchy. | All Users |
Scheduled Window Setup | Â Create / Update Delete | Schedule Windows (for Project execution) can be created, updated, or deleted. | FD Administrators |
Target Group | Â Read | Target Group can be read. Read permission can be overridden for individual Target Groups as well. Target Group is set of similar technology systems that you will deploy to in various Environments. | All Users |
Target Group | Â Create | Target Group can be created. | FD Administrators |
Target Group | Update / Delete | Target Group can be updated, or deleted. Update permission can be overridden for individual Target Groups as well. | FD Administrators Technical Leads for individual target groups |
User | Read | User information can be read. Users management is restricted to Administrator users. | All Users |
Webhook Functions | Read | Webhook functions can be read. | All Users |
Webhook Functions | Create / Update | Webhook functions can be created and updated. | Technical Leads, Developers |
Webhook Functions | Delete | Webhook functions can be deleted. | Technical Leads / FD Administrators |
Webhook Listener | Read | Webhook Listener can be read. | All Users |
Webhook Listener | Create / Update | Webhook Listener can be created or updated. | Technical Leads / FD Administrators |
Webhook Messages | Read - View Tracking | Webhook messages screen can be viewed. | All Users |
Webhook Messages | View Logs | Webhook message logs can be viewed. | Technical Leads, Developers |
Webhook Messages | View Content | Webhook message payload, query params and headers can be viewed. | Technical Leads, Developers |
Webhook Messages | Execute - Resubmit Message | Webhook message can be resubmitted. | Technical Leads, Developers |
Webhook Providers | Read | Webhook providers can be viewed. | All Users |
Webhook Providers | Create / Update | Webhook providers can be created and updated. | Technical Leads, Developers |
Work Item | Create / Modify Fields | Work Items can be created and fields can be modified, such as assignee, status, type etc. | Technical Leads, Developers |
Work Item | Delete | Work Items can be deleted. | Technical Leads / FD Administrators |
Work Item | Comments and Attachment Create | Fields cannot be modified but comments and attachments can be added. | All Users |
Workflow | Â Read | Workflow (build, deploy, test etc.) can be read. This contains execution code for build and deployment. | All Users |
Workflow | Â Create / Update | Workflow (build, deploy, test etc.) can be created or updated. This contains execution code for build and deployment. | FD Administrators |
1 - Release level permissions can be setup for individual release.
- style