Skip to main content

Risk-based access: Implementing custom attribute matchers


Technote (troubleshooting)


Problem(Abstract)

There is an update to the risk-based access documentation, which currently states that the supportsAttribute() and match() functions are required for custom attribute matchers.

Resolving the problem

The two functions, supportsAttribute() and match() are not mandatory for implementing custom attribute matchers.

In the risk-based access information center, on the page titled Implementing custom attribute matchers, under the section, Procedure, step 1 currently states:

Write the required JavaScript code in a file. Each JavaScript file must define the following two functions:

  • supportsAttribute()
  • match()

Instead, this statement must be replaced with:

Initialize two variables in the script, processed and matched, to indicate the status of the attribute processing and matching. For example: processed = true and matched = "MATCHED".


Related information

Risk-based access information center

Rate this page:

(0 users)Average rating

Copyright and trademark information

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Rate this page:


(0 users)Average rating

Add comments

Document information

Tivoli Federated Identity Manager


Software version:
6.2.2


Operating system(s):
AIX, Linux, Windows


Reference #:
1622505


Modified date:
2013-01-17

Translate my page

Content navigation