ReadMe.md #2

  • //
  • guest/
  • tom_tyler/
  • sw/
  • main/
  • SSO_Cutover/
  • ReadMe.md
  • Markdown
  • View
  • Commits
  • Open Download .zip Download (2 KB)

SSO Cutover Support Tools

This contains SSO Cutover support utilities.

Status: Prototype

While deemed prototype and not officially supported, the scripts here have been tested in at least one production-like sandbox environment.

Files in Here

This requires the P4 Server Deployment Package (SDP).

All files related to SSO cutover are deployed to the /p4/common/site/sso_cutover directory on a live system (or a sandbox for testing).

Main Files

  • SSO_Cutover.sh - The primary SSO cutover script. See the docs here.
  • enable_sso_for_ap_users.sh - A script added to the crontab by SSO_Cutover.sh.

Extra Stuff

  • SSO_Cutover.command_summary.txt, docs for SSO_Cutovver.sh; same as what you get by running SSO_Cutover.sh -man. See docs here.
  • logging.lib, a copy of an SDP so this can be self-contained and not reliant SDP versions.
  • runlib.lib, a copy of something typically deployed to /p4/common/lib so this can be self-contained and not reliant SDP versions.
  • p4_group_members.sh, a stand-alone utility to display the list of members in a P4 group, including recursive subgroup processing.
  • ReadMe.md - this file.
  • TestUtility-ResetToBaseline.sh, test support utility -- not needed for deployment.
  • enable_sso_for_ap_users.sh, a script to add to crontab after to add newly provisioned users. DO NOT USE if using SCIM with P4AS. See docs here.

Introduction

This is intended to be a one-stop shopping for everything needed to support the final production cutover to the P4Authentication Service after it has first been operating in "Pilot mode," with only a few brave test pilot users using SSO. Thus, this assumes the P4 Authentication Service is already installed, working, and provden to work for all client types -- command line, P4 Code Review, P4V, etc.

This relies on several assumptions about how SSO is to be used. This should be reviewed carefully and tested in a copy-of-production sandbox environment prior to use in live production.

Support Status

This SSO_Cutover software is Community Supported by the P4 Consulting team, meaning it is curated by the Consulting Team at Perforce Software. It is not officially supported by Perforce Software.

# SSO Cutover Support Tools

This contains SSO Cutover support utilities.

## Status: Prototype

While deemed prototype and not officially supported, the scripts here have been tested in at least one production-like sandbox environment.

## Files in Here

This requires the [P4 Server Deployment Package (SDP)](https://workshop.perforce.com/projects/perforce-software-sdp).

All files related to SSO cutover are deployed to the `/p4/common/site/sso_cutover` directory on a live system (or a sandbox for testing).

### Main Files

* `SSO_Cutover.sh` - The primary SSO cutover script. See [the docs here](SSO_Cutover.command_summary.txt).
* `enable_sso_for_ap_users.sh` - A script added to the crontab by `SSO_Cutover.sh`.

### Extra Stuff
* `SSO_Cutover.command_summary.txt`, docs for `SSO_Cutovver.sh`; same as what you get by running `SSO_Cutover.sh -man`. [See docs here](SSO_Cutover.command_summary.txt).
* `logging.lib`, a copy of an SDP so this can be self-contained and not reliant SDP versions.
* `runlib.lib`, a copy of something typically deployed to /p4/common/lib so this can be self-contained and not reliant SDP versions.
* `p4_group_members.sh`, a stand-alone utility to display the list of members in a P4 group, including recursive subgroup processing.
* `ReadMe.md` - this file.
* `TestUtility-ResetToBaseline.sh`, test support utility -- not needed for deployment.
* `enable_sso_for_ap_users.sh`, a script to add to crontab after to add newly provisioned users. DO NOT USE if using SCIM with P4AS. [See docs here](enable_sso_for_ap_users.command_summary.txt).

## Introduction

This is intended to be a one-stop shopping for everything needed to support the final production cutover to the P4Authentication Service after it has first been operating in "Pilot mode," with only a few brave test pilot users using SSO.  Thus, this assumes the P4 Authentication Service is already installed, working, and provden to work for all client types -- command line, P4 Code Review, P4V, etc.

This relies on several assumptions about how SSO is to be used.  This should be reviewed carefully and tested in a copy-of-production sandbox environment prior to use in live production.

## Support Status

This SSO_Cutover software is Community Supported by [the P4 Consulting team](mailto:p4consulting@perforce.com), meaning it is curated by the Consulting Team at Perforce Software.  It is _not_ officially supported by Perforce Software.
# Change User Description Committed
#2 32666 C. Thomas Tyler Added newest script.
#1 32665 C. Thomas Tyler Updated latest updates from after QA testing was completed and validation in a live environment.