IMPLEMENTATION
APPROACH

The following high implementation approach
will be followed when deploying the
MyPass solution.

 

IMPLEMENTATION APPROACH

The following high implementation approach will be followed when deploying the MyPass solution.

 

THE APPROACH

  • Stakeholders
  • Network details
  • Active directory details
  • Details for other connected systems being integrated enrolment details
  • (approach)
  • Change details
  • Deploy customer MyPass gateway
  • Create customer tenant on MyPass
  • Small pilot group testing
  • Integration signoff
  • Engage customer change team
  • Activate enrolment strategy
  • Go live with pilot group
  • And you’re off!
  • Stakeholders
  • Network details
  • Active directory details
  • Details for other connected systems being integrated enrolment details
  • (approach)
  • Change details
  • Deploy customer MyPass gateway
  • Create customer tenant on MyPass
  • Small pilot group testing
  • Integration signoff
  • Engage customer change team
  • Activate enrolment strategy
  • Go live with pilot group
  • And you’re off!

IMPLEMENTATION INFORMATION

DESCRIPTION    ACCOUNTABILITY
Before commencement of the project it is important to understand which systems the MyPass solution will be integrated with. For standard applications such as AD, SAP, SQL, Oracle etc., the integration process is straightforward. Further investigation will be required for lesser-known or undocumented systems. Mutual
DESCRIPTION    ACCOUNTABILITY
The deployment of a MyPass Gateway within the customer infrastructure facilitates secure password operations on customer systems. The gateway requires the following:

  • Hardware: single / dual core processor – 2/4 GB RAM – 60GB OS Drive
  • Software: Windows Server 2012 R2 – IIS Role
  • Network: Internet published 443 to the server with an external DNS record (A record)
  • Security: an SSL certificate of your choice to the external hostname
Customer
DESCRIPTION    ACCOUNTABILITY
The gateway package can be easily installed by Integralis, or in conjunction with the customer. Mutual
DESCRIPTION    ACCOUNTABILITY
In order to integrate the gateway into the on premise Active Directory the following is required:

  • Service Account: an account with the rights to read AD (normal user account) and reset passwords
  • User Group: a group that targets which on premise users are allowed to use the solution
  • Domain Info: information regarding the FQDN, NetBIOS, LDAP Search Base of the domain integrated
Customer
DESCRIPTION    ACCOUNTABILITY
As part of the SQL-based solution the following is required:

  • Server details: SQL Server / Instance
  • Authentication details: are the users we are resetting SQL Log-ins on the SQL server itself or are they users within a database on the server
  • Database details: if the target is a set of users within a database on the server, we require a method of resetting the password (SQL Stored Procedure or SQL Table / Encryption details)
Customer
DESCRIPTION    ACCOUNTABILITY
The customer MyPass tenant is created on the platform and default configuration is updated to use all the details as provided Integralis
DESCRIPTION    ACCOUNTABILITY
We conduct a limited test with the customer (2-3 users) on both the AD and SQL targets Mutual
DESCRIPTION    ACCOUNTABILITY
Use the Integralis-developed change management approach to ensure maximum user uptake on the solution once deployed. This will include:

  • Identifying the stakeholders
  • Creating awareness of the product and its advantages
  • Creating incentives to use the system
  • Sharing knowledge on how and why to use the system
  • Having the ability to implement the change
  • Re-enforcing the above steps
Mutual
DESCRIPTION    ACCOUNTABILITY
The customer is then given a 1xweek period to test with AD and SQL users Customer
DESCRIPTION    ACCOUNTABILITY
At the end of the deployment we conduct the following:

  • Evaluate the key success factors as agreed at the start of the project
  • Sign off the project
Mutual

download_button

IMPLEMENTATION INFORMATION

DESCRIPTION

Before commencement of the project it is important to understand which systems the MyPass solution will be integrated with. For standard applications such as AD, SAP, SQL, Oracle etc., the integration process is straightforward. Further investigation will be required for lesser-known or undocumented systems.

ACCOUNTABILITY

Mutual

DESCRIPTION

The deployment of a MyPass Gateway within the customer infrastructure facilitates secure password operations on customer systems. The gateway requires the following:

  • Hardware: single / dual core processor – 2/4 GB RAM – 60GB OS Drive
  • Software: Windows Server 2012 R2 – IIS Role
  • Network: Internet published 443 to the server with an external DNS record (A record)
  • Security: an SSL certificate of your choice to the external hostname

ACCOUNTABILITY

Customer

DESCRIPTION

The gateway package can be easily installed by Integralis, or in conjunction with the customer.

ACCOUNTABILITY

Mutual

DESCRIPTION

In order to integrate the gateway into the on premise Active Directory the following is required:

  • Service Account: an account with the rights to read AD (normal user account) and reset passwords
  • User Group: a group that targets which on premise users are allowed to use the solution
  • Domain Info: information regarding the FQDN, NetBIOS, LDAP Search Base of the domain integrated

ACCOUNTABILITY

Customer

DESCRIPTION

As part of the SQL-based solution the following is required:

  • Server details: SQL Server / Instance
  • Authentication details: are the users we are resetting SQL Log-ins on the SQL server itself or are they users within a database on the server
  • Database details: if the target is a set of users within a database on the server, we require a method of resetting the password (SQL Stored Procedure or SQL Table / Encryption details)

ACCOUNTABILITY

Customer

DESCRIPTION

The customer MyPass tenant is created on the platform and default configuration is updated to use all the details as provided

ACCOUNTABILITY

Integralis

DESCRIPTION

We conduct a limited test with the customer (2-3 users) on both the AD and SQL targets

ACCOUNTABILITY

Mutual

DESCRIPTION

Use the Integralis-developed change management approach to ensure maximum user uptake on the solution once deployed. This will include:

  • Identifying the stakeholders
  • Creating awareness of the product and its advantages
  • Creating incentives to use the system
  • Sharing knowledge on how and why to use the system
  • Having the ability to implement the change
  • Re-enforcing the above steps

ACCOUNTABILITY

Mutual

DESCRIPTION

The customer is then given a 1xweek period to test with AD and SQL users

ACCOUNTABILITY

Customer

DESCRIPTION

At the end of the deployment we conduct the following:

  • Evaluate the key success factors as agreed at the start of the project
  • Sign off the project

ACCOUNTABILITY

Mutual

download_button