|
1 | | -# This is a sample configuration file for the okta connector type. |
2 | | -# |
3 | | -# Okta is an identity hosting company that supports being the Identity Provider |
4 | | -# for Adobe Enterprise Federated ID. |
5 | | -# |
6 | | -# This sample file contains all of the settable options for this protocol. |
7 | | -# It is recommended that you make a copy of this file and edit it for your needs. |
8 | | -# While you are at it, you will likely want to remove a lot of this commentary, |
9 | | -# in order to enhance the readability of your file. |
| 1 | +# This is a template configuration file for the Okta directory connector |
| 2 | +# Learn more here: https://adobe-apiplatform.github.io/user-sync.py/en/user-manual/connect_okta.html |
10 | 3 |
|
11 | | -# connection settings (required) |
12 | | -# You must specify both of these settings. The token should be protected. |
13 | | -# For more information on getting an Okta API Token, see: |
14 | | -# http://developer.okta.com/docs/api/getting_started/getting_a_token.html |
15 | | -host: "sample-817042.oktapreview.com" |
16 | | -api_token: "00R_KJEaIcgAswrlO_sample_ZdgxC5scYZn8IZ-zi" |
17 | | - |
18 | | -# (required) group_filter_format (default given below) |
19 | | -# specifies the string format used to construct a group query. |
20 | | -# {group} is replaced with the name of the group to find. |
21 | | -group_filter_format: "{group}" |
| 4 | +# --- General Options --- |
| 5 | +# See https://adobe-apiplatform.github.io/user-sync.py/en/user-manual/connect_okta.html#general-options |
22 | 6 |
|
23 | | -# (required) all_users_filter (default given below) |
24 | | -# specifies the string filter used to find all users in the directory. |
25 | | -# Filter Examples: |
26 | | -# Filter user based on countryCode attribute in user profile |
27 | | -# all_users_filter: 'user.profile.countryCode == "MX"' |
28 | | -# Filter user based on status of ACTIVE |
29 | | -# all_users_filter: 'user.status == "ACTIVE"' |
30 | | -all_users_filter: 'user.status == "ACTIVE"' |
31 | | - |
32 | | -# (optional) default_identity_type (no default) |
33 | | -# specifies the identity type of the dashboard user to create. |
34 | | -# the valid values are: enterpriseID, federatedID |
35 | | -# If not specified, the default identity type from the main config file is used. |
36 | 7 | # user_identity_type: federatedID |
| 8 | +# string_encoding: utf8 |
37 | 9 |
|
38 | | -# (optional) string_encoding (default value given below) |
39 | | -# string_encoding specifies the Unicode string encoding used by the directory. |
40 | | -# All values retrieved from the directory are converted to Unicode before being |
41 | | -# sent to or compared with values on the Adobe side, to avoid encoding issues. |
42 | | -# The value must be a Python codec name or alias, such as 'latin1' or 'big5'. |
43 | | -# See https://docs.python.org/2/library/codecs.html#standard-encodings for details. |
44 | | -#string_encoding: utf8 |
45 | | - |
46 | | -# (optional) user_identity_type_format (no default) |
47 | | -# user_identity_type_format specifies how to construct a user's desired identity |
48 | | -# type on the Adobe side by combining constant strings with attribute values. |
49 | | -# Any names in curly braces are take as attribute names, and everything including |
50 | | -# the braces will be replaced on a per-user basis with the values of the attributes. |
51 | | -# There is no default value for this setting, because most directories don't contain |
52 | | -# users with different identity types (so setting the default identity type suffices). |
53 | | -# If your directory contains users of different identity types, you should define |
54 | | -# this field to look at the value of an appropriate attribute in your okta user profile. |
55 | | -# For example, if your Okta user profile attribute "idType" had one of the values |
56 | | -# adobe, enterprise, or federated in it for each user, you could use: |
57 | | -#user_identity_type_format: "{idType}ID" |
| 10 | +# --- API Options --- |
| 11 | +# See https://adobe-apiplatform.github.io/user-sync.py/en/user-manual/connect_okta.html#authentication |
58 | 12 |
|
59 | | -# (optional) user_email_format (default value given below) |
60 | | -# user_email_format specifies how to construct a user's email address by |
61 | | -# combining constant strings with the values of specific Okta profile attributes. |
62 | | -# Any names in curly braces are taken as attribute names, and everything including |
63 | | -# the braces will be replaced on a per-user basis with the values of the attributes. |
64 | | -# The default value is from "email" field in Okta user profile. |
65 | | -# NOTE: for this and every format setting, the constant strings must be in |
66 | | -# the encoding specified by the string_encoding setting, above. |
67 | | -user_email_format: "{email}" |
68 | | - |
69 | | -# (optional) user_domain_format (no default value) |
70 | | -# user_domain_format is analogous to user_email_format in syntax, but it |
71 | | -# is used to discover the domain for a given user. If not specified, the |
72 | | -# domain is taken from the domain part of the user's email address. |
73 | | -#user_domain_format: "{domain}" |
| 13 | +host: "sample-817042.oktapreview.com" |
| 14 | +api_token: "00R_KJEaIcgAswrlO_sample_ZdgxC5scYZn8IZ-zi" |
74 | 15 |
|
75 | | -# (optional) user_username_format (no default value) |
76 | | -# user_username_format specifies how to construct a user's username on the |
77 | | -# Adobe side by combining constant strings with attribute values. |
78 | | -# Any names in curly braces are taken as attribute names, and everything including |
79 | | -# the braces will be replaced on a per-user basis with the values of the attributes. |
80 | | -# This setting should only be used when you are using federatedID and your |
81 | | -# federation configuration specifies username-based login. In all other cases, |
82 | | -# make sure this is not set or returns an empty value, and the user's username |
83 | | -# will be taken from the user's email. |
84 | | -# This example supposes that the department and user_id are concatenated to |
85 | | -# produce a unique username for each user. |
86 | | -#user_username_format: "{department}_{user_id}" |
| 16 | +# --- User Filter Options --- |
| 17 | +# See https://adobe-apiplatform.github.io/user-sync.py/en/user-manual/connect_okta.html#user-filter-options |
87 | 18 |
|
88 | | -# (optional) user_given_name_format (default value given below) |
89 | | -# user_given_name_format specifies how to construct a user's given name by |
90 | | -# combining constant strings with the values of specific Okta profile attributes. |
91 | | -# Any names in curly braces are taken as attribute names, and everything including |
92 | | -# the braces will be replaced on a per-user basis with the values of the attributes. |
93 | | -# The default value is from "firstName" field in Okta user profile.. |
94 | | -# NOTE: for this and every format setting, the constant strings must be in |
95 | | -# the encoding specified by the string_encoding setting, above. |
96 | | -#user_given_name_format: "{firstName}" |
| 19 | +group_filter_format: "{group}" |
| 20 | +all_users_filter: 'user.status == "ACTIVE"' |
97 | 21 |
|
98 | | -# (optional) user_surname_format (default value given below) |
99 | | -# user_surname_format specifies how to construct a user's surname by |
100 | | -# combining constant strings with the values of specific Okta profile attributes. |
101 | | -# Any names in curly braces are taken as attribute names, and everything including |
102 | | -# the braces will be replaced on a per-user basis with the values of the attributes. |
103 | | -# The default value is from "lastName" field in Okta user profile. |
104 | | -# NOTE: for this and every format setting, the constant strings must be in |
105 | | -# the encoding specified by the string_encoding setting, above. |
106 | | -#user_surname_format: "{lastName}" |
| 22 | +# --- Column Mapping Options --- |
| 23 | +# See https://adobe-apiplatform.github.io/user-sync.py/en/user-manual/connect_okta.html#attribute-mapping-options |
107 | 24 |
|
108 | | -# (optional) user_country_code_format (default value given below) |
109 | | -# user_country_code_format specifies how to construct a user's country code by |
110 | | -# combining constant strings with the values of specific Okta profile attributes. |
111 | | -# Any names in curly braces are taken as attribute names, and everything including |
112 | | -# the braces will be replaced on a per-user basis with the values of the attributes. |
113 | | -# The default value is from "countryCode" field in Okta user profile. |
114 | | -# NOTE: for this and every format setting, the constant strings must be in |
115 | | -# the encoding specified by the string_encoding setting, above. |
116 | | -#user_country_code_format: "{countryCode}" |
| 25 | +user_email_format: "{email}" |
| 26 | +# user_identity_type_format: "{idType}ID" |
| 27 | +# user_domain_format: "{domain}" |
| 28 | +# user_username_format: "{department}_{user_id}" |
| 29 | +# user_given_name_format: "{firstName}" |
| 30 | +# user_surname_format: "{lastName}" |
| 31 | +# user_country_code_format: "{countryCode}" |
0 commit comments