Please enable JavaScript.

Coggle requires JavaScript to display documents.

Federation Documentation - Coggle Diagram

- - - - Working on deploying application with Terraform
      - Contacted Cheqroom technician to confirm if OIDC is an option? They replied with no, so we proceed with SAML
    - - Less painful because this is a new application
      - Licensing team already communicated that they desire SSO. Vendor is aware of licensing's desires and was able to better communicate the technical requirements
      - Lisam initially provisioned users with the wrong domain (jw.org), but because we are early in the process, they are going to change it
  - - - Licensing is main contact, but initial request was from AVS. They submitted a ticket, and we happened to ask Natasha (Licensing), who helped reevaluate the work because Figma is used my more departments.
      - Slowed down by lack of internet email for Jim
      - Concerns regarding when to schedule the migration, supporting that process, planning communication and potential rollback strategy
    - - Licensing initially requested SSO from Orchestration. They did not understand that federation doesn't necessarily include SCIM (System for Cross-domain Identity Management) or license management.
      - Two different applications: Bluebeam and Bluebeam Cloud
        
        Cloud app: deployed by CMS team, approved via mr by us
      - Already using manually created accounts, but they have the option to use a smaller subset of users for testing. However, they don't support a testing environent.
    - - Vendor communicated the workflow. We would provide them a list of accounts, and they would migrate the accounts from jw.org domain to bethel.jw.org in their application. Then we agreed we would schedule a date to deploy the federation. However, they deployed the federation without notifying us.
        
        Users reported that they had issues signing into the application. Some could still use jw.org instead of bethel acct. Others were asked to create new password.
        
        Some users had to "start over" with the new account
      - Communication with this vendor was very difficult (slow to respond). Stella (licensing) was very diligent with communication.
      - We didn't know if the vendor had a rollback plan or not.
      - In this case, there was an existing business relationship with Watchtower Licensing and Trimble. However, when we discussed SSO, we learned that Trimble didnt communicate internally between their technical team and their account manager team.