EAServer roles are mapped to Enterprise Security roles in the security.properties file. The following role mappings are created automatically by the Enterprise Security installer in security.properties:
easerverRolemap.epdefault_0.epdn=PortalWebPlugin easerverRolemap.epdefault_0.jagrole=PortalWebPlugin easerverRolemap.epdefault_1.epdn=PortalSecOfficer easerverRolemap.epdefault_1.jagrole=PortalSecurityOfficer easerverRolemap.epdefault_2.epdn=PortalAdmin easerverRolemap.epdefault_2.jagrole=PortalAdmin easerverRolemap.epdefault_3.epdn=PortalGuest easerverRolemap.epdefault_3.jagrole=PortalGuest
In earlier versions of Enterprise Security, roles were mapped using their names; beginning with version 6.0, you must use the DN instead of the name. For each of these pre-mapped Enterprise Security roles, the role DN is the same as the role name.
Mapping EAServer roles to Enterprise Security
roles
Using any standard ASCII text editor, open the security.properties file, which is located in the java/classes/com/sybase/ep/security subdirectory of your EAServer installation, and use this syntax to add a role mapping pair:
easerverRolemap.epdefault_n.epdn=secRoleDN easerverRolemap.epdefault_n.jagrole=EAServerRole
where:
n is an
integer that creates a unique mapping key (epdefault_n)
secRoleDN is the DN of the Enterprise Security role
EAServerRole is the name of the corresponding EAServer role
For example, the following lines map a role called NewRole using the Enterprise Security role DN and the EAServer role name:
easerverRolemap.epdefault_4.epdn=r1\=NewRole,o\=Sybase,c\=US easerverRolemap.epdefault_4.jagrole=NewRole
Stop and restart EAServer for the changes to take effect.
