v3.9.1 v3.9 v3.8.4 v3.8.3 v3.8.2 v3.8.1 v3.8 v3.7.2 v3.7.1 v3.7 v3.6
Auto Light Dark
Auto Light Dark
v3.9.1 v3.9 v3.8.4 v3.8.3 v3.8.2 v3.8.1 v3.8 v3.7.2 v3.7.1 v3.7 v3.6

Dynamically assigned journey based on CP usage scenario ( user logon type )

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:

image-20240210-123052.png

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)

Last updated: