eTSAPUserGroupValidFrom / eTSAPUserGroupValidTo - Greater than and Less than operators not working
search cancel

eTSAPUserGroupValidFrom / eTSAPUserGroupValidTo - Greater than and Less than operators not working

book

Article ID: 219088

calendar_today

Updated On:

Products

CA Identity Suite CA Identity Manager

Issue/Introduction

We are not able to use the Greater than or Less than operators in LDAP search filter for eTSAPUserGroupValidFrom or eTSAPUserGroupValidTo.

Thanks

Environment

Release : 14.x

Component : IdentityMinder(Identity Manager)

Cause

eTSAPUserGroupValidFrom (as well as eTSAPUserGroupValidTo) are both defined as String on in the schema - you can check this by running dumpptt on the SAP parser file

C:\CA\Identity Manager\Provisioning Server\bin>dumpptt.exe -f -t ..\data\sapparse.ptt -of d:\temp\sapptt.txt

    ATTRIBUTE (LDAP Name) eTSAPAccount::eTSAPUserGroupValidFrom
        User-friendly Name : SAPUserGroupValidFrom
        Description: First valid date
        ProhibitedCharacters: (null)
        MinValue: (null)
        MaxValue: (null)
        DefaultValue: (null)
        MinLength: 0
        MaxLength: 8
        EditType: 0 [string]
        MergeAlgorithm: 
        IsSpaceAllowedIn: yes
        IsAsciiOnly: no
        IsMultiValued: no
        Case: 0 [insensitive]
        Values: <NONE>
        ExcludedValues: <NONE>
        OrWords: <NONE>
        VerbReqs: <NONE>
        Group: (null)
        Label: (null)
        IsHidden: no
        IsRelationalOperatorAllowedWith: no
        IsEncrypted: no
        IsIndexed: no
        IsBaseAttribute: no
        Searchable: yes
        Incremental: no
        Obscured: no
        Deprecated: no
        DataLocation: 1 [AGENT]
        AuthOps: 0x14 (Modify, Owner)
        AuthAlias: (null)
        IsPropagationAllowed: yes
        IsPolicySync: no
        GlobalUserAttribute: (null)
        DependsOn: <NONE>

Since it is defined as a string, it does not support greater than / less than comparison attempts.

Resolution

With this being the designed configuration, it would require an Enhancement Request (Idea) for the change to be considered by Product Management.

In the meantime, to get the required functionality, proceed by mapping these attributes to a custom global user field (and possibly IM too) so the date could be used in the PX, as needed.