Clarity

Expand all | Collapse all

Clarity PPM SaaS Transition: GCP Authentication Methods - Part 3

  • 1.  Clarity PPM SaaS Transition: GCP Authentication Methods - Part 3

    Broadcom Employee
    Posted 03-30-2020 11:37 AM

    Welcome to the Clarity PPM SaaS Transition Blog series. This blog series provides customers updates regarding the Clarity PPM SaaS transition to the Google Cloud Platform™ (GCP).  In the first five blogs, Broadcom provided updates on various aspects of the migration including the overview, pre-transition activities, the actual transition process, and the various authentication methods available in GCP. 


    In this post, Broadcom will focus on some common questions customers ask us around GCP authentication methods. Prior to reading this blog, we recommend you read the following blogs:


    Clarity PPM SaaS Transition: GCP Authentication Methods - Part 1


    Clarity PPM SaaS Transition: GCP Authentication Methods - Part 2


    Frequently Asked Questions

    1. Our organization currently uses the CA On-Demand portal to update user information by using Integration adapters. This file updates user access and other information. How will this process work in the GCP data center?

    Answer: In the GCP data center, users will be managed directly from the Resources page in Clarity PPM or optionally via XOG for bulk creation and update. From a SaaS perspective, Clarity PPM includes the new SaaS User Sync job to synchronize users from Clarity to Okta.


    2. Our organization currently modifies information such as user name, email, and resource manager through the CA On-Demand portal. How will we do this in the GCP data center?

    Answer: In the GCP data center, Administrators will update user information directly within Clarity PPM using the Resources page or optionally via XOG.

     3. An automatic job runs in the  CA On-Demand portal to synchronize users between the portal and Clarity PPM. How will this work in the GCP data center?

    Answer: In the GCP data center, administrators create users directly within Clarity PPM and run the User Sync job to synchronize users from Clarity PPM to Okta. Administrators access the Reports and Jobs page to run the job in Clarity PPM.

            4. Our organization uses the On-Demand portal to process the Active Directory (AD) file and process new non-licensed users and agency           users that would bypass the portal. How will this be supported?

    Answer: In the GCP data center, administrators manage (create and update) licensed users directly within Clarity PPM. Administrators can work with Broadcom to configure licensed users to access Clarity PPM either through Okta or your company's active directory. If administrators want to use Okta, they can create a user in Clarity PPM SaaS and run the User Sync job to synchronize users in Okta. If they want to leverage the federated SSO option, they can use the information provided here.

    5. We currently use the OnDemand User Management (ODUM) tool to provision multiple Clarity PPM users through the portal. How will we do this in the GCP data center?

     

    Answer: In the GCP data center,  administrators can use the XOG utility to make bulk user changes in Clarity PPM. The ODUM tool will not be available in the GCP data center.

     6. Currently, we use custom scripts written in Python and Java to provision users via the On-Demand portal? How will this work in the GCP data center?

    Answer: In the GCP data center, Administrators can create and manage users in the Clarity PPM by using XOG. Administrators can then use the Sync SaaS Users job to synchronize users between Clarity PPM and Okta.


           7. Currently, we use the On-Demand Portal to create tenant user accounts and passwords. We then share the passwords with our testing                teams. Will we get tenant administrative access to manage Okta passwords?

    Answer: The On-Demand portal is not available in the GCP data center. All user data will be maintained directly in Clarity PPM and synchronized with Okta by using the SaaS User Sync job. 


           8. Currently, we have created usernames with an email address that are not associated with an actual mailbox and are not valid. Since Okta           uses email addresses to send login credentials how will it support our scenario?

    Answer: When you create a user in Clarity PPM and run the SaaS User Sync job to synchronize the user in Okta. Okta uses the email address and sends an email with the login credentials. If the system does not have a valid email address, Okta cannot send the email. 


          9. The SaaS User Sync job synchronizes users between Clarity and Okta. The job ignores all usernames that are not in the form of an email          address. If our organization is not using SSO, will Broadcom perform the updates necessary to make the usernames Okta compliant?

    Answer: Broadcom cannot make any data changes in any customer environment without coordinating directly with customers. Please discuss this topic with the assigned Broadcom point of contact (PoC). The Broadcom team will update usernames in coordination with your team. 


    This concludes Part 3 of the GCP Authentication Methods post. Thank you for being a part of the Clarity PPM community. Please write to clarityppm.saas@broadcom.com in case you have any specific questions for us. The next blog will be published on April 6th.

    #ca_clarity_ppm #gcp #clarityppmsaas

    ------------------------------
    Thanks & Regards
    Suman Pramanik
    Sr. Principal Support Engineer | Customer Success & Support, Enterprise Software Division
    Broadcom
    ------------------------------


  • 2.  RE: Clarity PPM SaaS Transition: GCP Authentication Methods - Part 3

    Former Employee
    Posted 03-30-2020 11:55 AM
    Thank you for sharing this update with the community Suman!

    ------------------------------
    Chris Hackett
    Community Manager, Broadcom Enterprise Software Division
    Broadcom Inc.
    ------------------------------