ZQ410 Unit 5 Transcript: Setting Up Server Security, Approvals, and Quality Gates
ZQ410 Unit 5 Transcript: Setting Up Server Security, Approvals, and Quality Gates
Slide 1
IBM UrbanCode Deploy uses a flexible team-based and role-based security model that maps to
your organizational structure. In this unit, you learn how to define and configure roles, set up
approvals and notifications, and use quality statuses and gates.
Slide 2
Objectives
▪ Describe the significance of a system team
▪ Create authorization realms, user groups, and teams
▪ Create and define roles and permissions
▪ Set up notifications and approvals
▪ Implement statuses and gates to ensure testing quality
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
Slide 3
Topics
• Configuring server security
• Setting up notifications
• Setting up an approval process
• Implementing statuses and gates to improve quality
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
Slide 4
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
From a high level, the security system for the server consists of an authorization realm,
authentication realm, roles, and teams.
The authentication realm verifies the identity of the user or system that is trying to log on to the
IBM UrbanCode Deploy server.
The authorization realm manages user groups. Roles manage permissions. Teams bring together
users with roles and specify which objects the team can access.
Slide 5
You can access the security system from any of these links on the Settings tab
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
Slide 6
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
Authorization realms verify the identity of a user or system attempting to login. There are three
available types for the server, internal storage authorization, an LDAP authorization realm, and an
SSO authorization realm:
• Internal storage authorization: Does not retrieve users from any external source. Instead,
you add users to internal storage authorization realms manually.
• LDAP authorization realm (Lightweight Directory Access Protocol): LDAP is a widely
used protocol for accessing distributed directory information over IP networks. It uses an
external LDAP server for authorization.
• SSO authorization realm (single sign-on): Uses an external server for authorization and
allows a user to sign on with one set of credentials for multiple applications.
Slide 7
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
Authentication realms manage users and determine user identity within authorization realms for
the server. Users can be created manually or imported from external systems, such as LDAP.
Slide 8
Role
Objects
Permissions
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
Permissions define what can be done; roles define who can do it. Separate permissions are
available for each type of object on the server, including components, applications, and
environments.
Slide 9
Group name
Group members
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
Groups are containers that grant permissions to multiple users; members automatically share a
group's permissions.
Slide 10
Keep the roles simple but ensure sufficiency for performing work
• Resources (view)
Release • Application (view, manage snapshots, run component applications)
Engineer • Environment (view, execute)
• Component (view)
• Resources (view)
• Application (view)
Approver • Environment (view, execute)
• Component (view)
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
When defining the roles for your team, start by keeping the roles simple, but make them sufficient
to perform the appropriate work.
10
Slide 11
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
You can grant a group of users the same role and permissions by dragging the group to the role.
11
Slide 12
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
You can also assign individuals to teams to give them the proper permissions.
12
Slide 13
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
You can assign an object, such as an application, to a team in the Team Object Mappings
section.
13
Slide 14
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
Security reports track information about roles and permissions. The application security report
shows the user roles and permissions that are set for applications.
14
Slide 15
Topics
• Configuring server security
• Setting up notifications
• Setting up an approval process
• Implementing statuses and gates to improve quality
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
15
Slide 16
Process failed!
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
Notifications are emails that are sent whenever user-defined trigger events on the server occur,
such as when a deployment finishes or an approval is required.
16
Slide 17
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
Before you can send notifications, users must have e-mail addresses attached to them on the
server; email addresses are not automatically imported.
17
Slide 18
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
To set up notifications, display the Notifications pane: click Settings > Notification Schemes.
18
Slide 19
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
When you set up the notification, you determine which users receive notification by selecting both
the triggering events and the role. The role is inherited from the security system.
19
Slide 20
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
You can assign notification schemes to applications and environments at creation or in the
Configuration tab.
20
Slide 21
Topics
• Configuring server security
• Setting up notifications
• Setting up an approval process
• Implementing statuses and gates to improve quality
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
21
Slide 22
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
An approval specifies the job that needs approval and the role of the approver. The main tasks for
setting up an approval process include selecting the notification scheme, enabling approvals on
an environment, and defining the approval process.
22
Slide 23
An approval process specifies the job that needs approval and the role of the
approver
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
To ensure that components cannot be deployed to the environment without first being approved,
select the require Approvals check box. This option enforces an approval process before the
deployment can be deployed to the environment. Approvals are usually attached to
environments.
23
Slide 24
When a request for approval is made, the users with the corresponding role are
notified through email
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
The approver can approve or reject a deployment, as well as provide comments to the decision.
24
Slide 25
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
You can see the status of the approvals by clicking Reports > Deployment Details.
25
Slide 26
Topics
• Configuring server security
• Setting up notifications
• Setting up an approval process
• Implementing environment gates to improve quality
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
26
Slide 27
Quality Verified
Ready for Testing
Deployment Ready
Necessary Bug Fix
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
An environment gate is a requirement that must be met before component versions can be
deployed to an environment. A version status adds a tag to a version to indicate that it has met
those requirements and can be deployed to the environment.
27
Slide 28
Select
Create Configure Add step in Check status
components
version environment component in Versions
with “latest
statuses gates process tab
with status”
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
When you set up gates, you first need to create the version statuses and configure the
environment gates. Then, you add a step in the component process to check the version status.
When you select the components for your deployment, choose “latest with status” prior to
deployment. This deploys only those versions that have met the appropriate status.
28
Slide 29
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
On the statuses tab, a table displays the currently configured version statuses. When you create
a status, you can set the required role field as a specific role to restrict the ability to assign a
status to a version.
29
Slide 30
Choose an environment
that requires gates, and
add conditions.
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
After you have your statuses configured, you can set up the application gates on your
environments. This is done from the application’s Configuration tab.
For each environment, you can set version statuses that the version must have before it can be
deployed to that environment. In this example, only versions that have the status “Ready for
Testing” are allowed to be deployed to the UAT environment.
30
Slide 31
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
You can add statuses to versions in component processes using the “Add Status to Version” step
in the IBM UrbanCode Deploy Versions plugin.
31
Slide 32
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
32
Slide 33
Shows when a
status was added
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
In order to view a version status, navigate to the component containing the version and then to
component’s versions tab. Click into the version. You’ll see a table containing the version’s
statuses and will be able to add or remove statuses from this interface.
33
Slide 34
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
When you select components for deployment, select “latest with status” to view the components
that have passed the gate.
34
Slide 35
Unit summary
• The security system for the server consists of an authentication realm, authorization
realm, roles, and teams
• Permissions define what can be done, not who can do it; roles define who can do it
• Users are granted permissions by being assigned to teams
• Notifications are emails that are sent whenever user-defined trigger events on the server
occur
• Approvals provide more visibility into deployments for audit trails
• An environment gate is a requirement that must be met before component versions can
be deployed to an environment
• Version statuses identify when component versions meet criteria
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
35
Slide 36
Unit 5: Setting up server security, approvals, and quality gates © Copyright IBM Corporation 2017
36