Passing an octetString attribute in a Workflow Search Activity results in an LDAP filter containing base64 value (4334192)

When configuring a Workflow Search Activity and filtering by any octetString type attribute, such as GUID, there are no results found, even when matching results are visually confirmed.

Reviewing the Active Roles Event Viewer logs show that the LDAP filter used by the search operation has a base64 encoded string instead of the expected GUID value.

WORKAROUND

Use a script to explicitly return a value in a STRING format, and search for that value.

For example:

function guidToString()
{
(get-qaduser $Workflow.Parameter("UserName") -DontUseDefaultIncludedProperties).guid.guid.toString()
} 

or

function guidToString($Request)
{
(get-qaduser $Request.dn -DontUseDefaultIncludedProperties).guid.guid.toString()
}

STATUS

Waiting for a fix in a future release of Active Roles.