Default Unwired Platform roles are logical roles that are built into the
system. While five roles are available by default for the 'admin' security
configuration
only three roles are necessary for enabling role-based access to administrative and DCN
interfaces.
Default
roles include:
- SUP Administrator – The platform administrator for the runtime and mobile artifacts. A required
role for the "admin" security configuration. See SUP Administrator and
SUP Domain Administrator.
- SUP Domain Administrator – The administrator assigned to a domain. A required role for the "admin"
security configuration. See SUP Administrator and SUP Domain
Administrator.
- SUP DCN User – The administrative user for DCNs. A required role for the "admin" security
configuration. This role must be mapped in *every* security configuration
assigned to deployed MBO packages that receive DCN requests. See SUP
DCN User Role.
- SUP
User,
SUP Developer – Sample
logical roles that have no impact on administration. Do not map these roles
or you may expose administration privileges inadvertently to
non-administration users.
All required administrative roles must be mapped for the "admin" security
configuration on the default domain, otherwise administrator authentication fails:
- In a development environment, mappings are automatically
created.
- In a production environment, physical roles must be added
manually to the directory used, and then manually mapped in Sybase Control
Center.
All optional maps may be mapped for the "admin" security configuration. However,
they may be required for custom configurations you create to authenticate
non-administrative users.
Note: Do not use the "admin" security configuration for the authentication of
development or application users. Also do not assign the admin security
configuration to any domain other than "default". The default domain is reserved for
administrative use only.