Jamf Connect Login (Okta)

—

—

—

Determines if users can bypass network authentication and use the Local Auth button at the loginwindow.

—

—

Allows local accounts to be migrated to network accounts. This is typically used when the user account was already created on the system, but you want the accounts to have the same username and password as the user's Okta identity.

—

—

—

—

—

—

The Redirect URI the user is sent to after successful authentication.

—

—

Determines if Jamf Connect Login displays a macOS style login screen instead of a window.

Text displayed when a user must enter a one time password (OTP).

—

—

A path to a local file that users can access by clicking the "Help" button in the Jamf Connect Login window.

Title of the end user license agreement

Subtitle of the end user license agreement

Text used for the end user license agreement (use three asterisks to create a line break in the text)

The path to a file storing the end user license agreement record

—

—

—

—

—

The arguments used with a specified script run by the RunScript mechanism

—

Specifies the IdP provider integrated with Jamf Connect Login.

—

The Client ID of the added app in you IdP used for authenticating the user's password via a resource owner password grant (ROPG) workflow. This value should match the OIDCClientID key.

Depends on: OIDCProvider

If set to true, the user must create a new password on the computer If set to false, the user must validate with their existing IdP password, which will also become the local password.

Depends on: OIDCProvider ∈ [GoogleID]

Determines which roles become an admin at the loginwindow. Users assigned a specified role become an admin at the loginwindow.

—

The client secret used by Jamf Connect Login and your IdP.

Depends on: OIDCProvider

—

—

When using the AuthUI rule, determines if the token cache is set to /tmp/cachedata.

—

—

—

—