okta.user.User
Explore with Pulumi AI
Creates an Okta User. This resource allows you to create and configure an Okta User.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as okta from "@pulumi/okta";
//## Full profile:
const example = new okta.user.User("example", {
firstName: "John",
lastName: "Smith",
login: "john.smith@example.com",
email: "john.smith@example.com",
city: "New York",
costCenter: "10",
countryCode: "US",
department: "IT",
displayName: "Dr. John Smith",
division: "Acquisitions",
employeeNumber: "111111",
honorificPrefix: "Dr.",
honorificSuffix: "Jr.",
locale: "en_US",
manager: "Jimbo",
managerId: "222222",
middleName: "John",
mobilePhone: "1112223333",
nickName: "Johnny",
organization: "Testing Inc.",
postalAddress: "1234 Testing St.",
preferredLanguage: "en-us",
primaryPhone: "4445556666",
profileUrl: "https://www.example.com/profile",
secondEmail: "john.smith.fun@example.com",
state: "NY",
streetAddress: "5678 Testing Ave.",
timezone: "America/New_York",
title: "Director",
userType: "Employee",
zipCode: "11111",
});
//## With Password Inline Hook:
const test2 = new okta.user.User("test2", {
firstName: "John",
lastName: "Smith",
login: "example@example.com",
email: "example@example.com",
passwordInlineHook: "default",
});
import pulumi
import pulumi_okta as okta
### Full profile:
example = okta.user.User("example",
first_name="John",
last_name="Smith",
login="john.smith@example.com",
email="john.smith@example.com",
city="New York",
cost_center="10",
country_code="US",
department="IT",
display_name="Dr. John Smith",
division="Acquisitions",
employee_number="111111",
honorific_prefix="Dr.",
honorific_suffix="Jr.",
locale="en_US",
manager="Jimbo",
manager_id="222222",
middle_name="John",
mobile_phone="1112223333",
nick_name="Johnny",
organization="Testing Inc.",
postal_address="1234 Testing St.",
preferred_language="en-us",
primary_phone="4445556666",
profile_url="https://www.example.com/profile",
second_email="john.smith.fun@example.com",
state="NY",
street_address="5678 Testing Ave.",
timezone="America/New_York",
title="Director",
user_type="Employee",
zip_code="11111")
### With Password Inline Hook:
test2 = okta.user.User("test2",
first_name="John",
last_name="Smith",
login="example@example.com",
email="example@example.com",
password_inline_hook="default")
package main
import (
"github.com/pulumi/pulumi-okta/sdk/v4/go/okta/user"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
// ## Full profile:
_, err := user.NewUser(ctx, "example", &user.UserArgs{
FirstName: pulumi.String("John"),
LastName: pulumi.String("Smith"),
Login: pulumi.String("john.smith@example.com"),
Email: pulumi.String("john.smith@example.com"),
City: pulumi.String("New York"),
CostCenter: pulumi.String("10"),
CountryCode: pulumi.String("US"),
Department: pulumi.String("IT"),
DisplayName: pulumi.String("Dr. John Smith"),
Division: pulumi.String("Acquisitions"),
EmployeeNumber: pulumi.String("111111"),
HonorificPrefix: pulumi.String("Dr."),
HonorificSuffix: pulumi.String("Jr."),
Locale: pulumi.String("en_US"),
Manager: pulumi.String("Jimbo"),
ManagerId: pulumi.String("222222"),
MiddleName: pulumi.String("John"),
MobilePhone: pulumi.String("1112223333"),
NickName: pulumi.String("Johnny"),
Organization: pulumi.String("Testing Inc."),
PostalAddress: pulumi.String("1234 Testing St."),
PreferredLanguage: pulumi.String("en-us"),
PrimaryPhone: pulumi.String("4445556666"),
ProfileUrl: pulumi.String("https://www.example.com/profile"),
SecondEmail: pulumi.String("john.smith.fun@example.com"),
State: pulumi.String("NY"),
StreetAddress: pulumi.String("5678 Testing Ave."),
Timezone: pulumi.String("America/New_York"),
Title: pulumi.String("Director"),
UserType: pulumi.String("Employee"),
ZipCode: pulumi.String("11111"),
})
if err != nil {
return err
}
// ## With Password Inline Hook:
_, err = user.NewUser(ctx, "test2", &user.UserArgs{
FirstName: pulumi.String("John"),
LastName: pulumi.String("Smith"),
Login: pulumi.String("example@example.com"),
Email: pulumi.String("example@example.com"),
PasswordInlineHook: pulumi.String("default"),
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Okta = Pulumi.Okta;
return await Deployment.RunAsync(() =>
{
//## Full profile:
var example = new Okta.User.User("example", new()
{
FirstName = "John",
LastName = "Smith",
Login = "john.smith@example.com",
Email = "john.smith@example.com",
City = "New York",
CostCenter = "10",
CountryCode = "US",
Department = "IT",
DisplayName = "Dr. John Smith",
Division = "Acquisitions",
EmployeeNumber = "111111",
HonorificPrefix = "Dr.",
HonorificSuffix = "Jr.",
Locale = "en_US",
Manager = "Jimbo",
ManagerId = "222222",
MiddleName = "John",
MobilePhone = "1112223333",
NickName = "Johnny",
Organization = "Testing Inc.",
PostalAddress = "1234 Testing St.",
PreferredLanguage = "en-us",
PrimaryPhone = "4445556666",
ProfileUrl = "https://www.example.com/profile",
SecondEmail = "john.smith.fun@example.com",
State = "NY",
StreetAddress = "5678 Testing Ave.",
Timezone = "America/New_York",
Title = "Director",
UserType = "Employee",
ZipCode = "11111",
});
//## With Password Inline Hook:
var test2 = new Okta.User.User("test2", new()
{
FirstName = "John",
LastName = "Smith",
Login = "example@example.com",
Email = "example@example.com",
PasswordInlineHook = "default",
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.okta.user.User;
import com.pulumi.okta.user.UserArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
//## Full profile:
var example = new User("example", UserArgs.builder()
.firstName("John")
.lastName("Smith")
.login("john.smith@example.com")
.email("john.smith@example.com")
.city("New York")
.costCenter("10")
.countryCode("US")
.department("IT")
.displayName("Dr. John Smith")
.division("Acquisitions")
.employeeNumber("111111")
.honorificPrefix("Dr.")
.honorificSuffix("Jr.")
.locale("en_US")
.manager("Jimbo")
.managerId("222222")
.middleName("John")
.mobilePhone("1112223333")
.nickName("Johnny")
.organization("Testing Inc.")
.postalAddress("1234 Testing St.")
.preferredLanguage("en-us")
.primaryPhone("4445556666")
.profileUrl("https://www.example.com/profile")
.secondEmail("john.smith.fun@example.com")
.state("NY")
.streetAddress("5678 Testing Ave.")
.timezone("America/New_York")
.title("Director")
.userType("Employee")
.zipCode("11111")
.build());
//## With Password Inline Hook:
var test2 = new User("test2", UserArgs.builder()
.firstName("John")
.lastName("Smith")
.login("example@example.com")
.email("example@example.com")
.passwordInlineHook("default")
.build());
}
}
resources:
### Full profile:
example:
type: okta:user:User
properties:
firstName: John
lastName: Smith
login: john.smith@example.com
email: john.smith@example.com
city: New York
costCenter: '10'
countryCode: US
department: IT
displayName: Dr. John Smith
division: Acquisitions
employeeNumber: '111111'
honorificPrefix: Dr.
honorificSuffix: Jr.
locale: en_US
manager: Jimbo
managerId: '222222'
middleName: John
mobilePhone: '1112223333'
nickName: Johnny
organization: Testing Inc.
postalAddress: 1234 Testing St.
preferredLanguage: en-us
primaryPhone: '4445556666'
profileUrl: https://www.example.com/profile
secondEmail: john.smith.fun@example.com
state: NY
streetAddress: 5678 Testing Ave.
timezone: America/New_York
title: Director
userType: Employee
zipCode: '11111'
### With Password Inline Hook:
test2:
type: okta:user:User
properties:
firstName: John
lastName: Smith
login: example@example.com
email: example@example.com
passwordInlineHook: default
Create User Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new User(name: string, args: UserArgs, opts?: CustomResourceOptions);
@overload
def User(resource_name: str,
args: UserArgs,
opts: Optional[ResourceOptions] = None)
@overload
def User(resource_name: str,
opts: Optional[ResourceOptions] = None,
email: Optional[str] = None,
login: Optional[str] = None,
last_name: Optional[str] = None,
first_name: Optional[str] = None,
mobile_phone: Optional[str] = None,
user_type: Optional[str] = None,
display_name: Optional[str] = None,
division: Optional[str] = None,
custom_profile_attributes_to_ignores: Optional[Sequence[str]] = None,
employee_number: Optional[str] = None,
expire_password_on_create: Optional[bool] = None,
custom_profile_attributes: Optional[str] = None,
old_password: Optional[str] = None,
honorific_suffix: Optional[str] = None,
country_code: Optional[str] = None,
locale: Optional[str] = None,
cost_center: Optional[str] = None,
manager: Optional[str] = None,
manager_id: Optional[str] = None,
middle_name: Optional[str] = None,
city: Optional[str] = None,
nick_name: Optional[str] = None,
honorific_prefix: Optional[str] = None,
department: Optional[str] = None,
primary_phone: Optional[str] = None,
password_hash: Optional[UserPasswordHashArgs] = None,
password_inline_hook: Optional[str] = None,
postal_address: Optional[str] = None,
preferred_language: Optional[str] = None,
password: Optional[str] = None,
profile_url: Optional[str] = None,
recovery_answer: Optional[str] = None,
recovery_question: Optional[str] = None,
second_email: Optional[str] = None,
skip_roles: Optional[bool] = None,
state: Optional[str] = None,
status: Optional[str] = None,
street_address: Optional[str] = None,
timezone: Optional[str] = None,
title: Optional[str] = None,
organization: Optional[str] = None,
zip_code: Optional[str] = None)
func NewUser(ctx *Context, name string, args UserArgs, opts ...ResourceOption) (*User, error)
public User(string name, UserArgs args, CustomResourceOptions? opts = null)
type: okta:user:User
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args UserArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args UserArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args UserArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args UserArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args UserArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var oktaUserResource = new Okta.User.User("oktaUserResource", new()
{
Email = "string",
Login = "string",
LastName = "string",
FirstName = "string",
MobilePhone = "string",
UserType = "string",
DisplayName = "string",
Division = "string",
CustomProfileAttributesToIgnores = new[]
{
"string",
},
EmployeeNumber = "string",
ExpirePasswordOnCreate = false,
CustomProfileAttributes = "string",
OldPassword = "string",
HonorificSuffix = "string",
CountryCode = "string",
Locale = "string",
CostCenter = "string",
Manager = "string",
ManagerId = "string",
MiddleName = "string",
City = "string",
NickName = "string",
HonorificPrefix = "string",
Department = "string",
PrimaryPhone = "string",
PasswordHash = new Okta.User.Inputs.UserPasswordHashArgs
{
Algorithm = "string",
Value = "string",
Salt = "string",
SaltOrder = "string",
WorkFactor = 0,
},
PasswordInlineHook = "string",
PostalAddress = "string",
PreferredLanguage = "string",
Password = "string",
ProfileUrl = "string",
RecoveryAnswer = "string",
RecoveryQuestion = "string",
SecondEmail = "string",
State = "string",
Status = "string",
StreetAddress = "string",
Timezone = "string",
Title = "string",
Organization = "string",
ZipCode = "string",
});
example, err := user.NewUser(ctx, "oktaUserResource", &user.UserArgs{
Email: pulumi.String("string"),
Login: pulumi.String("string"),
LastName: pulumi.String("string"),
FirstName: pulumi.String("string"),
MobilePhone: pulumi.String("string"),
UserType: pulumi.String("string"),
DisplayName: pulumi.String("string"),
Division: pulumi.String("string"),
CustomProfileAttributesToIgnores: pulumi.StringArray{
pulumi.String("string"),
},
EmployeeNumber: pulumi.String("string"),
ExpirePasswordOnCreate: pulumi.Bool(false),
CustomProfileAttributes: pulumi.String("string"),
OldPassword: pulumi.String("string"),
HonorificSuffix: pulumi.String("string"),
CountryCode: pulumi.String("string"),
Locale: pulumi.String("string"),
CostCenter: pulumi.String("string"),
Manager: pulumi.String("string"),
ManagerId: pulumi.String("string"),
MiddleName: pulumi.String("string"),
City: pulumi.String("string"),
NickName: pulumi.String("string"),
HonorificPrefix: pulumi.String("string"),
Department: pulumi.String("string"),
PrimaryPhone: pulumi.String("string"),
PasswordHash: &user.UserPasswordHashArgs{
Algorithm: pulumi.String("string"),
Value: pulumi.String("string"),
Salt: pulumi.String("string"),
SaltOrder: pulumi.String("string"),
WorkFactor: pulumi.Int(0),
},
PasswordInlineHook: pulumi.String("string"),
PostalAddress: pulumi.String("string"),
PreferredLanguage: pulumi.String("string"),
Password: pulumi.String("string"),
ProfileUrl: pulumi.String("string"),
RecoveryAnswer: pulumi.String("string"),
RecoveryQuestion: pulumi.String("string"),
SecondEmail: pulumi.String("string"),
State: pulumi.String("string"),
Status: pulumi.String("string"),
StreetAddress: pulumi.String("string"),
Timezone: pulumi.String("string"),
Title: pulumi.String("string"),
Organization: pulumi.String("string"),
ZipCode: pulumi.String("string"),
})
var oktaUserResource = new User("oktaUserResource", UserArgs.builder()
.email("string")
.login("string")
.lastName("string")
.firstName("string")
.mobilePhone("string")
.userType("string")
.displayName("string")
.division("string")
.customProfileAttributesToIgnores("string")
.employeeNumber("string")
.expirePasswordOnCreate(false)
.customProfileAttributes("string")
.oldPassword("string")
.honorificSuffix("string")
.countryCode("string")
.locale("string")
.costCenter("string")
.manager("string")
.managerId("string")
.middleName("string")
.city("string")
.nickName("string")
.honorificPrefix("string")
.department("string")
.primaryPhone("string")
.passwordHash(UserPasswordHashArgs.builder()
.algorithm("string")
.value("string")
.salt("string")
.saltOrder("string")
.workFactor(0)
.build())
.passwordInlineHook("string")
.postalAddress("string")
.preferredLanguage("string")
.password("string")
.profileUrl("string")
.recoveryAnswer("string")
.recoveryQuestion("string")
.secondEmail("string")
.state("string")
.status("string")
.streetAddress("string")
.timezone("string")
.title("string")
.organization("string")
.zipCode("string")
.build());
okta_user_resource = okta.user.User("oktaUserResource",
email="string",
login="string",
last_name="string",
first_name="string",
mobile_phone="string",
user_type="string",
display_name="string",
division="string",
custom_profile_attributes_to_ignores=["string"],
employee_number="string",
expire_password_on_create=False,
custom_profile_attributes="string",
old_password="string",
honorific_suffix="string",
country_code="string",
locale="string",
cost_center="string",
manager="string",
manager_id="string",
middle_name="string",
city="string",
nick_name="string",
honorific_prefix="string",
department="string",
primary_phone="string",
password_hash={
"algorithm": "string",
"value": "string",
"salt": "string",
"salt_order": "string",
"work_factor": 0,
},
password_inline_hook="string",
postal_address="string",
preferred_language="string",
password="string",
profile_url="string",
recovery_answer="string",
recovery_question="string",
second_email="string",
state="string",
status="string",
street_address="string",
timezone="string",
title="string",
organization="string",
zip_code="string")
const oktaUserResource = new okta.user.User("oktaUserResource", {
email: "string",
login: "string",
lastName: "string",
firstName: "string",
mobilePhone: "string",
userType: "string",
displayName: "string",
division: "string",
customProfileAttributesToIgnores: ["string"],
employeeNumber: "string",
expirePasswordOnCreate: false,
customProfileAttributes: "string",
oldPassword: "string",
honorificSuffix: "string",
countryCode: "string",
locale: "string",
costCenter: "string",
manager: "string",
managerId: "string",
middleName: "string",
city: "string",
nickName: "string",
honorificPrefix: "string",
department: "string",
primaryPhone: "string",
passwordHash: {
algorithm: "string",
value: "string",
salt: "string",
saltOrder: "string",
workFactor: 0,
},
passwordInlineHook: "string",
postalAddress: "string",
preferredLanguage: "string",
password: "string",
profileUrl: "string",
recoveryAnswer: "string",
recoveryQuestion: "string",
secondEmail: "string",
state: "string",
status: "string",
streetAddress: "string",
timezone: "string",
title: "string",
organization: "string",
zipCode: "string",
});
type: okta:user:User
properties:
city: string
costCenter: string
countryCode: string
customProfileAttributes: string
customProfileAttributesToIgnores:
- string
department: string
displayName: string
division: string
email: string
employeeNumber: string
expirePasswordOnCreate: false
firstName: string
honorificPrefix: string
honorificSuffix: string
lastName: string
locale: string
login: string
manager: string
managerId: string
middleName: string
mobilePhone: string
nickName: string
oldPassword: string
organization: string
password: string
passwordHash:
algorithm: string
salt: string
saltOrder: string
value: string
workFactor: 0
passwordInlineHook: string
postalAddress: string
preferredLanguage: string
primaryPhone: string
profileUrl: string
recoveryAnswer: string
recoveryQuestion: string
secondEmail: string
state: string
status: string
streetAddress: string
timezone: string
title: string
userType: string
zipCode: string
User Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The User resource accepts the following input properties:
- Email string
- User primary email address
- First
Name string - User first name
- Last
Name string - User last name
- Login string
- User Okta login
- City string
- User city
- Cost
Center string - User cost center
- Country
Code string - User country code
- Custom
Profile stringAttributes - JSON formatted custom attributes for a user. It must be JSON due to various types Okta allows.
- Custom
Profile List<string>Attributes To Ignores - Department string
- User department
- Display
Name string - User display name, suitable to show end users
- Division string
- User division
- Employee
Number string - User employee number
- Expire
Password boolOn Create - If set to
true
, the user will have to change the password at the next login. This property will be used when user is being created and works only whenpassword
field is set. Default:false
- Honorific
Prefix string - User honorific prefix
- Honorific
Suffix string - User honorific suffix
- Locale string
- User default location
- Manager string
- Manager of User
- Manager
Id string - Manager ID of User
- Middle
Name string - User middle name
- Mobile
Phone string - User mobile phone number
- Nick
Name string - User nickname
- Old
Password string - Old User Password. Should be only set in case the password was not changed using the provider. fter successful password change this field should be removed and
password
field should be used for further changes. - Organization string
- User organization
- Password string
- User Password
- Password
Hash UserPassword Hash - Specifies a hashed password to import into Okta.
- Password
Inline stringHook - Specifies that a Password Import Inline Hook should be triggered to handle verification of the user's password the first time the user logs in. This allows an existing password to be imported into Okta directly from some other store. When updating a user with a password hook the user must be in the
STAGED
status. Thepassword
field should not be specified when using Password Import Inline Hook. - Postal
Address string - User mailing address
- Preferred
Language string - User preferred language
- Primary
Phone string - User primary phone number
- Profile
Url string - User online profile (web page)
- Recovery
Answer string - User Password Recovery Answer
- Recovery
Question string - User Password Recovery Question
- Second
Email string - User secondary email address, used for account recovery
- Skip
Roles bool - Do not populate user roles information (prevents additional API call)
- State string
- User state or region
- Status string
- User profile property. Valid values are
ACTIVE
,DEPROVISIONED
,STAGED
,SUSPENDED
. Default:ACTIVE
- Street
Address string - User street address
- Timezone string
- User default timezone
- Title string
- User title
- User
Type string - User employee type
- Zip
Code string - User zipcode or postal code
- Email string
- User primary email address
- First
Name string - User first name
- Last
Name string - User last name
- Login string
- User Okta login
- City string
- User city
- Cost
Center string - User cost center
- Country
Code string - User country code
- Custom
Profile stringAttributes - JSON formatted custom attributes for a user. It must be JSON due to various types Okta allows.
- Custom
Profile []stringAttributes To Ignores - Department string
- User department
- Display
Name string - User display name, suitable to show end users
- Division string
- User division
- Employee
Number string - User employee number
- Expire
Password boolOn Create - If set to
true
, the user will have to change the password at the next login. This property will be used when user is being created and works only whenpassword
field is set. Default:false
- Honorific
Prefix string - User honorific prefix
- Honorific
Suffix string - User honorific suffix
- Locale string
- User default location
- Manager string
- Manager of User
- Manager
Id string - Manager ID of User
- Middle
Name string - User middle name
- Mobile
Phone string - User mobile phone number
- Nick
Name string - User nickname
- Old
Password string - Old User Password. Should be only set in case the password was not changed using the provider. fter successful password change this field should be removed and
password
field should be used for further changes. - Organization string
- User organization
- Password string
- User Password
- Password
Hash UserPassword Hash Args - Specifies a hashed password to import into Okta.
- Password
Inline stringHook - Specifies that a Password Import Inline Hook should be triggered to handle verification of the user's password the first time the user logs in. This allows an existing password to be imported into Okta directly from some other store. When updating a user with a password hook the user must be in the
STAGED
status. Thepassword
field should not be specified when using Password Import Inline Hook. - Postal
Address string - User mailing address
- Preferred
Language string - User preferred language
- Primary
Phone string - User primary phone number
- Profile
Url string - User online profile (web page)
- Recovery
Answer string - User Password Recovery Answer
- Recovery
Question string - User Password Recovery Question
- Second
Email string - User secondary email address, used for account recovery
- Skip
Roles bool - Do not populate user roles information (prevents additional API call)
- State string
- User state or region
- Status string
- User profile property. Valid values are
ACTIVE
,DEPROVISIONED
,STAGED
,SUSPENDED
. Default:ACTIVE
- Street
Address string - User street address
- Timezone string
- User default timezone
- Title string
- User title
- User
Type string - User employee type
- Zip
Code string - User zipcode or postal code
- email String
- User primary email address
- first
Name String - User first name
- last
Name String - User last name
- login String
- User Okta login
- city String
- User city
- cost
Center String - User cost center
- country
Code String - User country code
- custom
Profile StringAttributes - JSON formatted custom attributes for a user. It must be JSON due to various types Okta allows.
- custom
Profile List<String>Attributes To Ignores - department String
- User department
- display
Name String - User display name, suitable to show end users
- division String
- User division
- employee
Number String - User employee number
- expire
Password BooleanOn Create - If set to
true
, the user will have to change the password at the next login. This property will be used when user is being created and works only whenpassword
field is set. Default:false
- honorific
Prefix String - User honorific prefix
- honorific
Suffix String - User honorific suffix
- locale String
- User default location
- manager String
- Manager of User
- manager
Id String - Manager ID of User
- middle
Name String - User middle name
- mobile
Phone String - User mobile phone number
- nick
Name String - User nickname
- old
Password String - Old User Password. Should be only set in case the password was not changed using the provider. fter successful password change this field should be removed and
password
field should be used for further changes. - organization String
- User organization
- password String
- User Password
- password
Hash UserPassword Hash - Specifies a hashed password to import into Okta.
- password
Inline StringHook - Specifies that a Password Import Inline Hook should be triggered to handle verification of the user's password the first time the user logs in. This allows an existing password to be imported into Okta directly from some other store. When updating a user with a password hook the user must be in the
STAGED
status. Thepassword
field should not be specified when using Password Import Inline Hook. - postal
Address String - User mailing address
- preferred
Language String - User preferred language
- primary
Phone String - User primary phone number
- profile
Url String - User online profile (web page)
- recovery
Answer String - User Password Recovery Answer
- recovery
Question String - User Password Recovery Question
- second
Email String - User secondary email address, used for account recovery
- skip
Roles Boolean - Do not populate user roles information (prevents additional API call)
- state String
- User state or region
- status String
- User profile property. Valid values are
ACTIVE
,DEPROVISIONED
,STAGED
,SUSPENDED
. Default:ACTIVE
- street
Address String - User street address
- timezone String
- User default timezone
- title String
- User title
- user
Type String - User employee type
- zip
Code String - User zipcode or postal code
- email string
- User primary email address
- first
Name string - User first name
- last
Name string - User last name
- login string
- User Okta login
- city string
- User city
- cost
Center string - User cost center
- country
Code string - User country code
- custom
Profile stringAttributes - JSON formatted custom attributes for a user. It must be JSON due to various types Okta allows.
- custom
Profile string[]Attributes To Ignores - department string
- User department
- display
Name string - User display name, suitable to show end users
- division string
- User division
- employee
Number string - User employee number
- expire
Password booleanOn Create - If set to
true
, the user will have to change the password at the next login. This property will be used when user is being created and works only whenpassword
field is set. Default:false
- honorific
Prefix string - User honorific prefix
- honorific
Suffix string - User honorific suffix
- locale string
- User default location
- manager string
- Manager of User
- manager
Id string - Manager ID of User
- middle
Name string - User middle name
- mobile
Phone string - User mobile phone number
- nick
Name string - User nickname
- old
Password string - Old User Password. Should be only set in case the password was not changed using the provider. fter successful password change this field should be removed and
password
field should be used for further changes. - organization string
- User organization
- password string
- User Password
- password
Hash UserPassword Hash - Specifies a hashed password to import into Okta.
- password
Inline stringHook - Specifies that a Password Import Inline Hook should be triggered to handle verification of the user's password the first time the user logs in. This allows an existing password to be imported into Okta directly from some other store. When updating a user with a password hook the user must be in the
STAGED
status. Thepassword
field should not be specified when using Password Import Inline Hook. - postal
Address string - User mailing address
- preferred
Language string - User preferred language
- primary
Phone string - User primary phone number
- profile
Url string - User online profile (web page)
- recovery
Answer string - User Password Recovery Answer
- recovery
Question string - User Password Recovery Question
- second
Email string - User secondary email address, used for account recovery
- skip
Roles boolean - Do not populate user roles information (prevents additional API call)
- state string
- User state or region
- status string
- User profile property. Valid values are
ACTIVE
,DEPROVISIONED
,STAGED
,SUSPENDED
. Default:ACTIVE
- street
Address string - User street address
- timezone string
- User default timezone
- title string
- User title
- user
Type string - User employee type
- zip
Code string - User zipcode or postal code
- email str
- User primary email address
- first_
name str - User first name
- last_
name str - User last name
- login str
- User Okta login
- city str
- User city
- cost_
center str - User cost center
- country_
code str - User country code
- custom_
profile_ strattributes - JSON formatted custom attributes for a user. It must be JSON due to various types Okta allows.
- custom_
profile_ Sequence[str]attributes_ to_ ignores - department str
- User department
- display_
name str - User display name, suitable to show end users
- division str
- User division
- employee_
number str - User employee number
- expire_
password_ boolon_ create - If set to
true
, the user will have to change the password at the next login. This property will be used when user is being created and works only whenpassword
field is set. Default:false
- honorific_
prefix str - User honorific prefix
- honorific_
suffix str - User honorific suffix
- locale str
- User default location
- manager str
- Manager of User
- manager_
id str - Manager ID of User
- middle_
name str - User middle name
- mobile_
phone str - User mobile phone number
- nick_
name str - User nickname
- old_
password str - Old User Password. Should be only set in case the password was not changed using the provider. fter successful password change this field should be removed and
password
field should be used for further changes. - organization str
- User organization
- password str
- User Password
- password_
hash UserPassword Hash Args - Specifies a hashed password to import into Okta.
- password_
inline_ strhook - Specifies that a Password Import Inline Hook should be triggered to handle verification of the user's password the first time the user logs in. This allows an existing password to be imported into Okta directly from some other store. When updating a user with a password hook the user must be in the
STAGED
status. Thepassword
field should not be specified when using Password Import Inline Hook. - postal_
address str - User mailing address
- preferred_
language str - User preferred language
- primary_
phone str - User primary phone number
- profile_
url str - User online profile (web page)
- recovery_
answer str - User Password Recovery Answer
- recovery_
question str - User Password Recovery Question
- second_
email str - User secondary email address, used for account recovery
- skip_
roles bool - Do not populate user roles information (prevents additional API call)
- state str
- User state or region
- status str
- User profile property. Valid values are
ACTIVE
,DEPROVISIONED
,STAGED
,SUSPENDED
. Default:ACTIVE
- street_
address str - User street address
- timezone str
- User default timezone
- title str
- User title
- user_
type str - User employee type
- zip_
code str - User zipcode or postal code
- email String
- User primary email address
- first
Name String - User first name
- last
Name String - User last name
- login String
- User Okta login
- city String
- User city
- cost
Center String - User cost center
- country
Code String - User country code
- custom
Profile StringAttributes - JSON formatted custom attributes for a user. It must be JSON due to various types Okta allows.
- custom
Profile List<String>Attributes To Ignores - department String
- User department
- display
Name String - User display name, suitable to show end users
- division String
- User division
- employee
Number String - User employee number
- expire
Password BooleanOn Create - If set to
true
, the user will have to change the password at the next login. This property will be used when user is being created and works only whenpassword
field is set. Default:false
- honorific
Prefix String - User honorific prefix
- honorific
Suffix String - User honorific suffix
- locale String
- User default location
- manager String
- Manager of User
- manager
Id String - Manager ID of User
- middle
Name String - User middle name
- mobile
Phone String - User mobile phone number
- nick
Name String - User nickname
- old
Password String - Old User Password. Should be only set in case the password was not changed using the provider. fter successful password change this field should be removed and
password
field should be used for further changes. - organization String
- User organization
- password String
- User Password
- password
Hash Property Map - Specifies a hashed password to import into Okta.
- password
Inline StringHook - Specifies that a Password Import Inline Hook should be triggered to handle verification of the user's password the first time the user logs in. This allows an existing password to be imported into Okta directly from some other store. When updating a user with a password hook the user must be in the
STAGED
status. Thepassword
field should not be specified when using Password Import Inline Hook. - postal
Address String - User mailing address
- preferred
Language String - User preferred language
- primary
Phone String - User primary phone number
- profile
Url String - User online profile (web page)
- recovery
Answer String - User Password Recovery Answer
- recovery
Question String - User Password Recovery Question
- second
Email String - User secondary email address, used for account recovery
- skip
Roles Boolean - Do not populate user roles information (prevents additional API call)
- state String
- User state or region
- status String
- User profile property. Valid values are
ACTIVE
,DEPROVISIONED
,STAGED
,SUSPENDED
. Default:ACTIVE
- street
Address String - User street address
- timezone String
- User default timezone
- title String
- User title
- user
Type String - User employee type
- zip
Code String - User zipcode or postal code
Outputs
All input properties are implicitly available as output properties. Additionally, the User resource produces the following output properties:
- id str
- The provider-assigned unique ID for this managed resource.
- raw_
status str - The raw status of the User in Okta - (status is mapped)
Look up Existing User Resource
Get an existing User resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: UserState, opts?: CustomResourceOptions): User
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
city: Optional[str] = None,
cost_center: Optional[str] = None,
country_code: Optional[str] = None,
custom_profile_attributes: Optional[str] = None,
custom_profile_attributes_to_ignores: Optional[Sequence[str]] = None,
department: Optional[str] = None,
display_name: Optional[str] = None,
division: Optional[str] = None,
email: Optional[str] = None,
employee_number: Optional[str] = None,
expire_password_on_create: Optional[bool] = None,
first_name: Optional[str] = None,
honorific_prefix: Optional[str] = None,
honorific_suffix: Optional[str] = None,
last_name: Optional[str] = None,
locale: Optional[str] = None,
login: Optional[str] = None,
manager: Optional[str] = None,
manager_id: Optional[str] = None,
middle_name: Optional[str] = None,
mobile_phone: Optional[str] = None,
nick_name: Optional[str] = None,
old_password: Optional[str] = None,
organization: Optional[str] = None,
password: Optional[str] = None,
password_hash: Optional[UserPasswordHashArgs] = None,
password_inline_hook: Optional[str] = None,
postal_address: Optional[str] = None,
preferred_language: Optional[str] = None,
primary_phone: Optional[str] = None,
profile_url: Optional[str] = None,
raw_status: Optional[str] = None,
recovery_answer: Optional[str] = None,
recovery_question: Optional[str] = None,
second_email: Optional[str] = None,
skip_roles: Optional[bool] = None,
state: Optional[str] = None,
status: Optional[str] = None,
street_address: Optional[str] = None,
timezone: Optional[str] = None,
title: Optional[str] = None,
user_type: Optional[str] = None,
zip_code: Optional[str] = None) -> User
func GetUser(ctx *Context, name string, id IDInput, state *UserState, opts ...ResourceOption) (*User, error)
public static User Get(string name, Input<string> id, UserState? state, CustomResourceOptions? opts = null)
public static User get(String name, Output<String> id, UserState state, CustomResourceOptions options)
resources: _: type: okta:user:User get: id: ${id}
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- City string
- User city
- Cost
Center string - User cost center
- Country
Code string - User country code
- Custom
Profile stringAttributes - JSON formatted custom attributes for a user. It must be JSON due to various types Okta allows.
- Custom
Profile List<string>Attributes To Ignores - Department string
- User department
- Display
Name string - User display name, suitable to show end users
- Division string
- User division
- Email string
- User primary email address
- Employee
Number string - User employee number
- Expire
Password boolOn Create - If set to
true
, the user will have to change the password at the next login. This property will be used when user is being created and works only whenpassword
field is set. Default:false
- First
Name string - User first name
- Honorific
Prefix string - User honorific prefix
- Honorific
Suffix string - User honorific suffix
- Last
Name string - User last name
- Locale string
- User default location
- Login string
- User Okta login
- Manager string
- Manager of User
- Manager
Id string - Manager ID of User
- Middle
Name string - User middle name
- Mobile
Phone string - User mobile phone number
- Nick
Name string - User nickname
- Old
Password string - Old User Password. Should be only set in case the password was not changed using the provider. fter successful password change this field should be removed and
password
field should be used for further changes. - Organization string
- User organization
- Password string
- User Password
- Password
Hash UserPassword Hash - Specifies a hashed password to import into Okta.
- Password
Inline stringHook - Specifies that a Password Import Inline Hook should be triggered to handle verification of the user's password the first time the user logs in. This allows an existing password to be imported into Okta directly from some other store. When updating a user with a password hook the user must be in the
STAGED
status. Thepassword
field should not be specified when using Password Import Inline Hook. - Postal
Address string - User mailing address
- Preferred
Language string - User preferred language
- Primary
Phone string - User primary phone number
- Profile
Url string - User online profile (web page)
- Raw
Status string - The raw status of the User in Okta - (status is mapped)
- Recovery
Answer string - User Password Recovery Answer
- Recovery
Question string - User Password Recovery Question
- Second
Email string - User secondary email address, used for account recovery
- Skip
Roles bool - Do not populate user roles information (prevents additional API call)
- State string
- User state or region
- Status string
- User profile property. Valid values are
ACTIVE
,DEPROVISIONED
,STAGED
,SUSPENDED
. Default:ACTIVE
- Street
Address string - User street address
- Timezone string
- User default timezone
- Title string
- User title
- User
Type string - User employee type
- Zip
Code string - User zipcode or postal code
- City string
- User city
- Cost
Center string - User cost center
- Country
Code string - User country code
- Custom
Profile stringAttributes - JSON formatted custom attributes for a user. It must be JSON due to various types Okta allows.
- Custom
Profile []stringAttributes To Ignores - Department string
- User department
- Display
Name string - User display name, suitable to show end users
- Division string
- User division
- Email string
- User primary email address
- Employee
Number string - User employee number
- Expire
Password boolOn Create - If set to
true
, the user will have to change the password at the next login. This property will be used when user is being created and works only whenpassword
field is set. Default:false
- First
Name string - User first name
- Honorific
Prefix string - User honorific prefix
- Honorific
Suffix string - User honorific suffix
- Last
Name string - User last name
- Locale string
- User default location
- Login string
- User Okta login
- Manager string
- Manager of User
- Manager
Id string - Manager ID of User
- Middle
Name string - User middle name
- Mobile
Phone string - User mobile phone number
- Nick
Name string - User nickname
- Old
Password string - Old User Password. Should be only set in case the password was not changed using the provider. fter successful password change this field should be removed and
password
field should be used for further changes. - Organization string
- User organization
- Password string
- User Password
- Password
Hash UserPassword Hash Args - Specifies a hashed password to import into Okta.
- Password
Inline stringHook - Specifies that a Password Import Inline Hook should be triggered to handle verification of the user's password the first time the user logs in. This allows an existing password to be imported into Okta directly from some other store. When updating a user with a password hook the user must be in the
STAGED
status. Thepassword
field should not be specified when using Password Import Inline Hook. - Postal
Address string - User mailing address
- Preferred
Language string - User preferred language
- Primary
Phone string - User primary phone number
- Profile
Url string - User online profile (web page)
- Raw
Status string - The raw status of the User in Okta - (status is mapped)
- Recovery
Answer string - User Password Recovery Answer
- Recovery
Question string - User Password Recovery Question
- Second
Email string - User secondary email address, used for account recovery
- Skip
Roles bool - Do not populate user roles information (prevents additional API call)
- State string
- User state or region
- Status string
- User profile property. Valid values are
ACTIVE
,DEPROVISIONED
,STAGED
,SUSPENDED
. Default:ACTIVE
- Street
Address string - User street address
- Timezone string
- User default timezone
- Title string
- User title
- User
Type string - User employee type
- Zip
Code string - User zipcode or postal code
- city String
- User city
- cost
Center String - User cost center
- country
Code String - User country code
- custom
Profile StringAttributes - JSON formatted custom attributes for a user. It must be JSON due to various types Okta allows.
- custom
Profile List<String>Attributes To Ignores - department String
- User department
- display
Name String - User display name, suitable to show end users
- division String
- User division
- email String
- User primary email address
- employee
Number String - User employee number
- expire
Password BooleanOn Create - If set to
true
, the user will have to change the password at the next login. This property will be used when user is being created and works only whenpassword
field is set. Default:false
- first
Name String - User first name
- honorific
Prefix String - User honorific prefix
- honorific
Suffix String - User honorific suffix
- last
Name String - User last name
- locale String
- User default location
- login String
- User Okta login
- manager String
- Manager of User
- manager
Id String - Manager ID of User
- middle
Name String - User middle name
- mobile
Phone String - User mobile phone number
- nick
Name String - User nickname
- old
Password String - Old User Password. Should be only set in case the password was not changed using the provider. fter successful password change this field should be removed and
password
field should be used for further changes. - organization String
- User organization
- password String
- User Password
- password
Hash UserPassword Hash - Specifies a hashed password to import into Okta.
- password
Inline StringHook - Specifies that a Password Import Inline Hook should be triggered to handle verification of the user's password the first time the user logs in. This allows an existing password to be imported into Okta directly from some other store. When updating a user with a password hook the user must be in the
STAGED
status. Thepassword
field should not be specified when using Password Import Inline Hook. - postal
Address String - User mailing address
- preferred
Language String - User preferred language
- primary
Phone String - User primary phone number
- profile
Url String - User online profile (web page)
- raw
Status String - The raw status of the User in Okta - (status is mapped)
- recovery
Answer String - User Password Recovery Answer
- recovery
Question String - User Password Recovery Question
- second
Email String - User secondary email address, used for account recovery
- skip
Roles Boolean - Do not populate user roles information (prevents additional API call)
- state String
- User state or region
- status String
- User profile property. Valid values are
ACTIVE
,DEPROVISIONED
,STAGED
,SUSPENDED
. Default:ACTIVE
- street
Address String - User street address
- timezone String
- User default timezone
- title String
- User title
- user
Type String - User employee type
- zip
Code String - User zipcode or postal code
- city string
- User city
- cost
Center string - User cost center
- country
Code string - User country code
- custom
Profile stringAttributes - JSON formatted custom attributes for a user. It must be JSON due to various types Okta allows.
- custom
Profile string[]Attributes To Ignores - department string
- User department
- display
Name string - User display name, suitable to show end users
- division string
- User division
- email string
- User primary email address
- employee
Number string - User employee number
- expire
Password booleanOn Create - If set to
true
, the user will have to change the password at the next login. This property will be used when user is being created and works only whenpassword
field is set. Default:false
- first
Name string - User first name
- honorific
Prefix string - User honorific prefix
- honorific
Suffix string - User honorific suffix
- last
Name string - User last name
- locale string
- User default location
- login string
- User Okta login
- manager string
- Manager of User
- manager
Id string - Manager ID of User
- middle
Name string - User middle name
- mobile
Phone string - User mobile phone number
- nick
Name string - User nickname
- old
Password string - Old User Password. Should be only set in case the password was not changed using the provider. fter successful password change this field should be removed and
password
field should be used for further changes. - organization string
- User organization
- password string
- User Password
- password
Hash UserPassword Hash - Specifies a hashed password to import into Okta.
- password
Inline stringHook - Specifies that a Password Import Inline Hook should be triggered to handle verification of the user's password the first time the user logs in. This allows an existing password to be imported into Okta directly from some other store. When updating a user with a password hook the user must be in the
STAGED
status. Thepassword
field should not be specified when using Password Import Inline Hook. - postal
Address string - User mailing address
- preferred
Language string - User preferred language
- primary
Phone string - User primary phone number
- profile
Url string - User online profile (web page)
- raw
Status string - The raw status of the User in Okta - (status is mapped)
- recovery
Answer string - User Password Recovery Answer
- recovery
Question string - User Password Recovery Question
- second
Email string - User secondary email address, used for account recovery
- skip
Roles boolean - Do not populate user roles information (prevents additional API call)
- state string
- User state or region
- status string
- User profile property. Valid values are
ACTIVE
,DEPROVISIONED
,STAGED
,SUSPENDED
. Default:ACTIVE
- street
Address string - User street address
- timezone string
- User default timezone
- title string
- User title
- user
Type string - User employee type
- zip
Code string - User zipcode or postal code
- city str
- User city
- cost_
center str - User cost center
- country_
code str - User country code
- custom_
profile_ strattributes - JSON formatted custom attributes for a user. It must be JSON due to various types Okta allows.
- custom_
profile_ Sequence[str]attributes_ to_ ignores - department str
- User department
- display_
name str - User display name, suitable to show end users
- division str
- User division
- email str
- User primary email address
- employee_
number str - User employee number
- expire_
password_ boolon_ create - If set to
true
, the user will have to change the password at the next login. This property will be used when user is being created and works only whenpassword
field is set. Default:false
- first_
name str - User first name
- honorific_
prefix str - User honorific prefix
- honorific_
suffix str - User honorific suffix
- last_
name str - User last name
- locale str
- User default location
- login str
- User Okta login
- manager str
- Manager of User
- manager_
id str - Manager ID of User
- middle_
name str - User middle name
- mobile_
phone str - User mobile phone number
- nick_
name str - User nickname
- old_
password str - Old User Password. Should be only set in case the password was not changed using the provider. fter successful password change this field should be removed and
password
field should be used for further changes. - organization str
- User organization
- password str
- User Password
- password_
hash UserPassword Hash Args - Specifies a hashed password to import into Okta.
- password_
inline_ strhook - Specifies that a Password Import Inline Hook should be triggered to handle verification of the user's password the first time the user logs in. This allows an existing password to be imported into Okta directly from some other store. When updating a user with a password hook the user must be in the
STAGED
status. Thepassword
field should not be specified when using Password Import Inline Hook. - postal_
address str - User mailing address
- preferred_
language str - User preferred language
- primary_
phone str - User primary phone number
- profile_
url str - User online profile (web page)
- raw_
status str - The raw status of the User in Okta - (status is mapped)
- recovery_
answer str - User Password Recovery Answer
- recovery_
question str - User Password Recovery Question
- second_
email str - User secondary email address, used for account recovery
- skip_
roles bool - Do not populate user roles information (prevents additional API call)
- state str
- User state or region
- status str
- User profile property. Valid values are
ACTIVE
,DEPROVISIONED
,STAGED
,SUSPENDED
. Default:ACTIVE
- street_
address str - User street address
- timezone str
- User default timezone
- title str
- User title
- user_
type str - User employee type
- zip_
code str - User zipcode or postal code
- city String
- User city
- cost
Center String - User cost center
- country
Code String - User country code
- custom
Profile StringAttributes - JSON formatted custom attributes for a user. It must be JSON due to various types Okta allows.
- custom
Profile List<String>Attributes To Ignores - department String
- User department
- display
Name String - User display name, suitable to show end users
- division String
- User division
- email String
- User primary email address
- employee
Number String - User employee number
- expire
Password BooleanOn Create - If set to
true
, the user will have to change the password at the next login. This property will be used when user is being created and works only whenpassword
field is set. Default:false
- first
Name String - User first name
- honorific
Prefix String - User honorific prefix
- honorific
Suffix String - User honorific suffix
- last
Name String - User last name
- locale String
- User default location
- login String
- User Okta login
- manager String
- Manager of User
- manager
Id String - Manager ID of User
- middle
Name String - User middle name
- mobile
Phone String - User mobile phone number
- nick
Name String - User nickname
- old
Password String - Old User Password. Should be only set in case the password was not changed using the provider. fter successful password change this field should be removed and
password
field should be used for further changes. - organization String
- User organization
- password String
- User Password
- password
Hash Property Map - Specifies a hashed password to import into Okta.
- password
Inline StringHook - Specifies that a Password Import Inline Hook should be triggered to handle verification of the user's password the first time the user logs in. This allows an existing password to be imported into Okta directly from some other store. When updating a user with a password hook the user must be in the
STAGED
status. Thepassword
field should not be specified when using Password Import Inline Hook. - postal
Address String - User mailing address
- preferred
Language String - User preferred language
- primary
Phone String - User primary phone number
- profile
Url String - User online profile (web page)
- raw
Status String - The raw status of the User in Okta - (status is mapped)
- recovery
Answer String - User Password Recovery Answer
- recovery
Question String - User Password Recovery Question
- second
Email String - User secondary email address, used for account recovery
- skip
Roles Boolean - Do not populate user roles information (prevents additional API call)
- state String
- User state or region
- status String
- User profile property. Valid values are
ACTIVE
,DEPROVISIONED
,STAGED
,SUSPENDED
. Default:ACTIVE
- street
Address String - User street address
- timezone String
- User default timezone
- title String
- User title
- user
Type String - User employee type
- zip
Code String - User zipcode or postal code
Supporting Types
UserPasswordHash, UserPasswordHashArgs
- Algorithm string
- The algorithm used to generate the hash using the password
- Value string
- For SHA-512, SHA-256, SHA-1, MD5, This is the actual base64-encoded hash of the password (and salt, if used). This is the Base64 encoded value of the SHA-512/SHA-256/SHA-1/MD5 digest that was computed by either pre-fixing or post-fixing the salt to the password, depending on the saltOrder. If a salt was not used in the source system, then this should just be the the Base64 encoded value of the password's SHA-512/SHA-256/SHA-1/MD5 digest. For BCRYPT, This is the actual radix64-encoded hashed password.
- Salt string
- Only required for salted hashes
- Salt
Order string - Specifies whether salt was pre- or postfixed to the password before hashing
- Work
Factor int - Governs the strength of the hash and the time required to compute it. Only required for BCRYPT algorithm
- Algorithm string
- The algorithm used to generate the hash using the password
- Value string
- For SHA-512, SHA-256, SHA-1, MD5, This is the actual base64-encoded hash of the password (and salt, if used). This is the Base64 encoded value of the SHA-512/SHA-256/SHA-1/MD5 digest that was computed by either pre-fixing or post-fixing the salt to the password, depending on the saltOrder. If a salt was not used in the source system, then this should just be the the Base64 encoded value of the password's SHA-512/SHA-256/SHA-1/MD5 digest. For BCRYPT, This is the actual radix64-encoded hashed password.
- Salt string
- Only required for salted hashes
- Salt
Order string - Specifies whether salt was pre- or postfixed to the password before hashing
- Work
Factor int - Governs the strength of the hash and the time required to compute it. Only required for BCRYPT algorithm
- algorithm String
- The algorithm used to generate the hash using the password
- value String
- For SHA-512, SHA-256, SHA-1, MD5, This is the actual base64-encoded hash of the password (and salt, if used). This is the Base64 encoded value of the SHA-512/SHA-256/SHA-1/MD5 digest that was computed by either pre-fixing or post-fixing the salt to the password, depending on the saltOrder. If a salt was not used in the source system, then this should just be the the Base64 encoded value of the password's SHA-512/SHA-256/SHA-1/MD5 digest. For BCRYPT, This is the actual radix64-encoded hashed password.
- salt String
- Only required for salted hashes
- salt
Order String - Specifies whether salt was pre- or postfixed to the password before hashing
- work
Factor Integer - Governs the strength of the hash and the time required to compute it. Only required for BCRYPT algorithm
- algorithm string
- The algorithm used to generate the hash using the password
- value string
- For SHA-512, SHA-256, SHA-1, MD5, This is the actual base64-encoded hash of the password (and salt, if used). This is the Base64 encoded value of the SHA-512/SHA-256/SHA-1/MD5 digest that was computed by either pre-fixing or post-fixing the salt to the password, depending on the saltOrder. If a salt was not used in the source system, then this should just be the the Base64 encoded value of the password's SHA-512/SHA-256/SHA-1/MD5 digest. For BCRYPT, This is the actual radix64-encoded hashed password.
- salt string
- Only required for salted hashes
- salt
Order string - Specifies whether salt was pre- or postfixed to the password before hashing
- work
Factor number - Governs the strength of the hash and the time required to compute it. Only required for BCRYPT algorithm
- algorithm str
- The algorithm used to generate the hash using the password
- value str
- For SHA-512, SHA-256, SHA-1, MD5, This is the actual base64-encoded hash of the password (and salt, if used). This is the Base64 encoded value of the SHA-512/SHA-256/SHA-1/MD5 digest that was computed by either pre-fixing or post-fixing the salt to the password, depending on the saltOrder. If a salt was not used in the source system, then this should just be the the Base64 encoded value of the password's SHA-512/SHA-256/SHA-1/MD5 digest. For BCRYPT, This is the actual radix64-encoded hashed password.
- salt str
- Only required for salted hashes
- salt_
order str - Specifies whether salt was pre- or postfixed to the password before hashing
- work_
factor int - Governs the strength of the hash and the time required to compute it. Only required for BCRYPT algorithm
- algorithm String
- The algorithm used to generate the hash using the password
- value String
- For SHA-512, SHA-256, SHA-1, MD5, This is the actual base64-encoded hash of the password (and salt, if used). This is the Base64 encoded value of the SHA-512/SHA-256/SHA-1/MD5 digest that was computed by either pre-fixing or post-fixing the salt to the password, depending on the saltOrder. If a salt was not used in the source system, then this should just be the the Base64 encoded value of the password's SHA-512/SHA-256/SHA-1/MD5 digest. For BCRYPT, This is the actual radix64-encoded hashed password.
- salt String
- Only required for salted hashes
- salt
Order String - Specifies whether salt was pre- or postfixed to the password before hashing
- work
Factor Number - Governs the strength of the hash and the time required to compute it. Only required for BCRYPT algorithm
Import
$ pulumi import okta:user/user:User example <user_id>
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- Okta pulumi/pulumi-okta
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
okta
Terraform Provider.