PayloadKit

Jamf Connect Login (Okta)

com.jamf.connect.login

Jamf Connect Login settings

macOS

Configuration Keys (42)

Showing 42 of 42 keys

KeyTypeDescriptionDefaultRange
string—Default: —Range: —
data—Default: —Range: —
string—Default: —Range: —
DenyLocalboolean
booleanDetermines if users can bypass network authentication and use the Local Auth button at the loginwindow.Default: —Range: —
array—Default: —Range: —
string

Username

string—Default: —Range: —
boolean—Default: —Range: —
Migrateboolean
booleanAllows 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.Default: —Range: —
array—Default: —Range: —
string

Username

string—Default: —Range: —
string—Default: —Range: —
string—Default: —Range: —
string—Default: —Range: —
boolean—Default: —Range: —
string—Default: —Range: —
stringThe Redirect URI the user is sent to after successful authentication.Default: "nomadoauth://oauth-callback/okta"Range: —
string—Default: —Range: —
booleanDetermines if Jamf Connect Login displays a macOS style login screen instead of a window.Default: —Range: —
stringText displayed when a user must enter a one time password (OTP).Default: —Range: —
HelpURLstring
string—Default: —Range: —
stringA path to a local file that users can access by clicking the "Help" button in the Jamf Connect Login window.Default: —Range: —
EULATitlestring

EULA Title

stringTitle of the end user license agreementDefault: "End User License Agreement"Range: —

EULA Subtitle

stringSubtitle of the end user license agreementDefault: "Terms and Conditions"Range: —
EULATextstring

EULA Text

stringText used for the end user license agreement (use three asterisks to create a line break in the text)Default: —Range: —
EULAPathstring

EULA Path

stringThe path to a file storing the end user license agreement recordDefault: —Range: —
boolean—Default: —Range: —
EnableFDEboolean
boolean—Default: —Range: —
boolean—Default: —Range: —
string—Default: —Range: —
string—Default: —Range: —
arrayThe arguments used with a specified script run by the RunScript mechanismDefault: —Range: —
string

Arguments

string—Default: —Range: —
boolean—Default: —Range: —
required
stringSpecifies the IdP provider integrated with Jamf Connect Login.Default: "Azure"Range: Microsoft Azure AD (Azure), Google Identity (GoogleID), IBM Cloud Identity (IBMCI), OneLogin (OneLogin), PingFederate (PingFederate), Custom (Custom)
required
string—Default: —Range: —
stringThe 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

Default: —Range: —
booleanIf 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]

Default: trueRange: —
arrayDetermines which roles become an admin at the loginwindow. Users assigned a specified role become an admin at the loginwindow.Default: —Range: —
string

Role

string—Default: —Range: —
string—Default: —Range: —
stringThe client secret used by Jamf Connect Login and your IdP.

Depends on: OIDCProvider

Default: —Range: —
string—Default: —Range: —
string—Default: —Range: —
booleanWhen using the AuthUI rule, determines if the token cache is set to /tmp/cachedata.Default: —Range: —