Dynamicly assigned journey based on CP usage scenario
Credential Provider is sending information back to server about current usage scenario. Possible values are:
CPUS_LOGON
CPUS_UNLOCK_WORKSTATION
CPUS_CHANGE_PASSWORD
CPUS_CREDUI
CPUS_LOGON_RDP (since 3.7)
CPUS_UNLOCK_WORKSTATION_RDP (since 3.7)
This allows to set journey ore granular - can be set for specific scenarios. using conditions in Orchestrator:
input.session.externalValues["credentialProviderUsageScenario"] == "CPUS_LOGON"
Predefined conditions are:
Usage scenario | Orchestrator condition | Description |
|---|---|---|
CPUS_LOGON | is_windows_authn_logon | Initial Logon |
CPUS_UNLOCK_WORKSTATION | is_windows_authn_unlock | Unlock |
CPUS_CREDUI | is_windows_authn_shell_extension | Shell Extension |
CPUS_LOGON_RDP | is_windows_authn_logon_rdp | Initial Logon, RDP |
CPUS_UNLOCK_WORKSTATION_RDP | is_windows_authn_unlock_rdp | Unlock, RDP (reconnect) |