
RFC 4072S
210 / 272
PHOENIX CONTACT
108580_en_02
•
Enable the check box of the user role(s) that you would like to assign to the user.
•
Click on the “Save” button to save the selected user role(s) for the user.
You can open PLCnext Engineer HMI applications with or without authentication. With
authentication, the user name and password are required.
Recommended:
•
If you do not wish to use authentication, use an upstream firewall (e.g., in a switch) to
enable access to the PLCnext Engineer HMI application only through certain
devices.
Detailed information on the prepared security functions in a PLCnext Engineer HMI appli-
cation as well as on using the EHmiLevelxx can be found in the online help of
PLCnext Engineer.
Table 9-1
User roles and their assigned access permissions in the various applications
Application or
component of the
RFC 4072S
Access permission
User role
Ad
m
in
Ce
r
tif
ic
ateMan
ager
UserManager
Engineer
Co
mmi
ssi
o
ne
r
Se
r
v
ic
e
Da
ta
Vie
w
er
Da
ta
Changer
Vie
w
er
EHmiL
e
v
e
lX
File R
e
ader
Fi
leW
r
it
er
EHmiVi
e
w
er
EHmiC
h
anger
SD card / parame-
terization memory
SFTP access to the file system with an SFTP
client
J
Shell
SSH access to the shell
J
PLCnext Engineer
View values in the cockpit (e.g., utilization, etc.)
J
J
J
J
J
J
J
PLCnext Engineer
Transfer a project to the controller
J
J
PLCnext Engineer
Start or stop the controller (cold/warm start)
J
J
J
J
PLCnext Engineer
Restart the controller (reboot)
J
PLCnext Engineer
Reset the controller to default setting type 1
J
PLCnext Engineer
View online variable values
J
J
J
J
J
J
PLCnext Engineer
Overwrite variables
J
J
J
J
PLCnext Engineer
Set and delete breakpoints
J
J
J
Please note:
Authentication with a user name and
password is
always
required for
SFTP access, even when user
authentication is disabled.
Please note:
Authentication with a user name and
password is
always
required for
SSH access, even when user
authentication is disabled.
Summary of Contents for RFC 4072S
Page 22: ...RFC 4072S 22 272 PHOENIX CONTACT 108580_en_02...
Page 68: ...RFC 4072S 68 272 PHOENIX CONTACT 108580_en_02...
Page 82: ...RFC 4072S 82 272 PHOENIX CONTACT 108580_en_02...
Page 142: ...RFC 4072S 142 272 PHOENIX CONTACT 108580_en_02...
Page 154: ...RFC 4072S 154 272 PHOENIX CONTACT 108580_en_02...
Page 222: ...RFC 4072S 222 272 PHOENIX CONTACT 108580_en_02...
Page 234: ...RFC 4072S 234 272 PHOENIX CONTACT 108580_en_02...
Page 254: ...RFC 4072S 254 272 PHOENIX CONTACT 108580_en_02...
Page 264: ...RFC 4072S 264 272 PHOENIX CONTACT 108580_en_02...
Page 268: ...RFC 4072S 268 272 PHOENIX CONTACT 108580_en_02...
Page 271: ......