IBM Verify

IBM Verify

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Getting data from Access Policy to an Authentication Mechanism InfoMap

    Posted Wed February 09, 2022 12:13 PM
    Hi,

    I'm trying to get some data which I have available in a federation access policy (through the protocolContext) to an authentication mechanism InfoMap.

    The way I am doing this now is by setting a redirectUri from the access policy with an added HTTP GET request parameter, which I can retrieve in the InfoMap.
    This works fine but I don't want the users to see the value in the URL, and be able to change it.

    Is there a good way to store data in the access policy which I can retrieve in the infomaps?
    Or is there any good documentation/guide available which explains how these components interact with eachother, and what kind of session data is available?

    Thanks

    ------------------------------
    Niel Verheire
    ------------------------------


  • 2.  RE: Getting data from Access Policy to an Authentication Mechanism InfoMap

    Posted Wed February 09, 2022 04:39 PM

    Hello Niel,

    Have you considered using the DMAP?
    https://www.ibm.com/docs/en/sva/10.0.3?topic=rules-javascript-whitelist
    com.tivoli.am.fim.trustserver.sts.utilities.IDMappingExtCacheDMAPImpl

    Here's an example of using the distributed map in an infomap:

    https://github.com/IBM-Security/isam-support/blob/master/config-example/aac/info_map_js/infomap_getAttributeFromDMAPCache.js

    The Java Documentation has information on how to utilize said cache.



    ------------------------------
    JACK YARBOROUGH
    ------------------------------



  • 3.  RE: Getting data from Access Policy to an Authentication Mechanism InfoMap

    Posted Thu February 10, 2022 04:54 AM
    Hi Jack,

    Thanks for your suggestion. That certainly seems like a better way.

    Got it working using the "user_session_id" header value. As this is before any authentication happens I was unable to use credential attributes.

    ------------------------------
    Niel Verheire
    ------------------------------