Okta -> Admin -> input username -> assign applications
Don't use the GUI for Okta tokens. Chris can generate a new Okta token with the correct user and access. Also, better to look in the bash history for Okta tokens
ldap.read@defpoint.com
is the Okta user that has the API token that Splunk uses to auth to Okta and pull logs. If the ldap.read account is suspended, the API token is suspended as well. The ldap.read
account's password expires after 60 days. To see when the password will expire, go to Reports -> Okta Password Health. Don't open with EXCEL! Add 60 days to the date in the last column.
ldap.read
username and the current password from Vault (engineering/root
). Three failed logins will lock the user. MFA is disabled for the account.engineering/root
with a key of ldap.read@defpoint.com
. You will have to create a new version of engineering/root to save the password.OKTA -> Reports -> Okta Password Health Open with Text editor Not excel
Fred ignored the above advice and created an okta API key for himself (Web UI: Admin->Security->API->Create Token
)
Then:
export OKTA_API_TOKEN=[token here]
terragrunt apply
Okta will rate limit us if we hit the API to frequently. This causes users to not be able to VPN in because the OpenVPN server cannot connect to the OKTA API in a timely manner. To see if this is happening you can log into OKTA and look for a banner indicating the rate limiting. We also pull logs into Moose Splunk via the OKTA API so you can run this Splunk search on Moose to see if we are getting errors. Finally, if you log into the OpenVPN and see timeout errors that is an indicator that OKTA is rate limiting us on the OKTA API.
index=_internal host=moose-splunk-hf* source=*okta* rate limit pausing operations
| timechart count
#Okta user create log index=auth sourcetype="OktaIM2:log" "Create okta user"