Credentials Mapping
The following topics describe how to use the credentials mapping function to authenticate and then manage users.
Authentication through Credentials Mapping
Credentials mapping (also known as authentication mapping) relies upon the fact that the web server or servlet has authenticated the user already. Then, given an authenticated username, Info*Engine obtains a map that defines the usernames and credentials that are to be sent to adapters or sent to the JMS MOM (if implemented at your site) on behalf of the authenticated user.
With a credentials mapping mechanism in place, Info*Engine can dynamically add authentication parameters to these webjects through a site-defined credentials mapping task or a set of credentials files.
The following rules apply to credentials mapping:
If the author of a task or JSP page explicitly specifies DBUSER and PASSWD parameters on a webject, those parameters take precedence over any other authentication information that might be available.
If DBUSER and PASSWD parameters are not explicitly specified, Info*Engine attempts to provide values for them from the credentials mapping information.
If no credentials mapping information is available, or if the credentials mapping does not provide valid DBUSER and PASSWD values for the JMS MOM or the adapter to which a webject is being routed, Info*Engine does not send any DBUSER or PASSWD values. In this case, the adapter obtains default values from its configuration properties, and the Info*Engine messaging software and the Web Event Service obtains default values from their configuration properties. If no default values are set, Info*Engine attempts anonymous access.
这对您有帮助吗?