Okta generates an invalid username error during provisioning in Okta Advanced Server Access (ASA) or Okta Privileged Access (OPA) when a user is assigned a reserved username. Resolve this issue by assigning a non-reserved username to the affected user. When attempting to provision a user with a reserved username, Okta displays the following error and image:

Automatic provisioning of user Service Account to app Okta Advanced Server Access failed: Error while creating user user@example.com: Bad Request. Errors reported by remote server: Invalid ASA username: service

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Advanced Server Access (ASA)
• Okta Privileged Access (OPA)

The error occurs because the assigned username is included in the list of reserved usernames for Okta Advanced Server Access (ASA) and Okta Privileged Access (OPA), which cannot be used for provisioning.

How is the invalid username provisioning error resolved?

Assign a non-reserved username to the affected user.

1. Change the username of the affected user to a value that is not included in the reserved usernames list.

Review the following list of case-insensitive reserved usernames that cannot be used in Okta Advanced Server Access (ASA) or Okta Privileged Access (OPA).

adm
man
mysql
named
netdump
network
news
nfsnobody
nis
nntp
noaccess
nobody
nobody4
nogroup
nscd
nt
ntlm
ntp
null
nuucp
operator
oracle
pcap
plugdev
postfix
postgres
proxy
pvm
quagga
radiusd
radvd
remote
rendszergazda
restricted
root
rpc
rpcuser
rpm
rsync
sasl
schannel
self
sendmail
server
service
sftd
shadow
shutdown
smmsp
squid
src
sshd
staff
sudo
sync
sys
system
tape
terminal
this
tty
ubuntu
users
utmp
uucp
vcsa
video
voice
webalizer
wnn
world
www
www-data
xfs
xpg
xpg4

Related References

• Reserved Group Names within ASA