The CAS Server supports the Endeca Access Control System which you can use to make your front-end Oracle Commerce application secure. This topic explains the details involved in making your Oracle Commerce application secure based on the ACL properties generated from your CMS repository.
To make use of the ACL properties generated by the CAS Server in your Oracle Commerce front-end application, take into account the following considerations:
The CAS Server tags each record with access control list (ACL) properties that it generates. The generated ACL properties are based on the corresponding properties for each entry in the CMS repository. In other words, the ACL properties generated by a crawl are based on ACL properties created by your CMS repository.
You can use manipulators to transform the generated ACL properties into the format for ACLs that is used by the Endeca Access Control System. You can then use the modified properties in conjunction with security login modules to limit access to records based on user or group login profiles. For details on using the Endeca Access Control System, see the Oracle Commerce Guided Search Security Guide.
Typically, the generated ACL properties, since they are based on the ACL information specific to a repository, can apply to either users or groups. If they apply to groups, the code for the Oracle Commerce front-end application has to map users to their corresponding groups.
