FAQ: Unified User Provisioning and Authentication: General
- What is UAM, UPAS and UPW? How are they related?
- Unified Provisioning and Authentication System (UPAS), is a Workday service designed to provide unified user provisioning and authentication across all Workday applications, including Adaptive Planning. Its main goal is to unify the authentication and identity management components between Workday core systems and acquired applications like Adaptive Planning.
- The User Provisioning Workspace (UPW) is a key component of UPAS, designed to provide centralized management and configuration for user access across various Workday applications, including Adaptive Planning.
- Unified Access Management (UAM) is a Workday service that provides centralized access management for Adaptive Planning through permission assignment and security group sync to Adaptive Planning.
- Is Proxy Login supported with UPAS?
- The proxy login feature is currently not available. We're working on delivering it in a future release.
- Is UAM required for UPAS?
- Yes, UAM is a prerequisite for UPAS configuration.
- I am already performing SSO and user sync through Workday HCM and Financials. Do I need to switch to UPAS?
- Yes, we recommend all customers to switch from the current SSO and user sync to UPAS because of its benefits.
- What are the benefits of UPAS?
- UPAS provides:
- A more unified and streamlined sign-in process with instance specific menu items.
- Direct sign-in using Adaptive Planning Instance-specific URLs.
- Real-time or hourly user sync and attribute updates for individual Adaptive Planning instances.
- Direct user sync to specific Adaptive Planning instances. The legacy user sync method sync only to the parent instance.
- Automatic instance assignment centrally managed through security groups. The legacy user sync method manually assigns instances.
- Direct access Adaptive Planning APIs using Workday access tokens.
- Simplified Workday tenant management configuration.
- Can I enable UPAS in a non-production environment to decide whether to enable it in production later?
- Yes, you can first enable UPAS in a non-production environment. However, when a refresh happens from production, UPAS configuration gets wiped out the non-production environment.
- How much downtime is required to implement UPAS?
- There is no downtime requirement for UPAS. During UPAS configuration, the current login and user sync continue to work until you flip the switch to UPAS.
- What steps do I need to take after the weekly sandbox refresh?
- No manual steps are required after the weekly sandbox refresh.