SQL issue between version 4 and version 5

[Mohamed Lrhazi]

and in the log, both in version 4 and 5, I see that the emplid is correct
in the sql statement:

shib-idp;idp-process.log;dev;nothing;                SELECT 1 FROM
PS_CX_TIMELYCAR_VW WHERE EMPLID = '1400621'

On Wed, Dec 18, 2024 at 4:03 PM Mohamed Lrhazi <lrhazi at cua.edu> wrote:

> and that attribute is defined like this, it comes from LDAP query.
>
> <AttributeDefinition id="employeeID" xsi:type="Simple">
> <InputDataConnector ref="adLdapConnector" attributeNames="employeeID" />
> <AttributeEncoder xsi:type="SAML2String" name=
> "urn:oid:0.9.2342.19200300.100.1.116"
> friendlyName="employeeID" encodeType="false" />
>
>
> On Wed, Dec 18, 2024 at 4:01 PM Mohamed Lrhazi <lrhazi at cua.edu> wrote:
>
>> just to clarify, $employeeID is an attribute reference like so:
>>
>> <InputAttributeDefinition ref="employeeID" />
>>
>> On Wed, Dec 18, 2024 at 3:10 PM Mohamed Lrhazi <lrhazi at cua.edu> wrote:
>>
>>> Hello,
>>>
>>>
>>> I am encountering an issue with the following code within an attribute
>>> definition:
>>>
>>> ```
>>> <QueryTemplate>
>>> <![CDATA[
>>> SELECT CASE WHEN EXISTS (
>>> SELECT 1 FROM PS_CX_TIMELYCAR_VW WHERE EMPLID = '$employeeID.get(0)'
>>> ) OR '$employeeID.get(0)' IN ('1400621', '1386568')
>>> THEN 'true' ELSE 'false' END AS isTimelycareEligible
>>> FROM DUAL
>>> ]]>
>>> </QueryTemplate>
>>> ```
>>>
>>> This code functions as expected in Shibboleth version 4, returning
>>> 'true' for a user with emplid 1400621. However, in Shibboleth version 5, it
>>> returns 'false' for the same user.
>>>
>>> Any idea what would be causing this? maybe $employeeID.get(0)' does not
>>> work the same way in version 5 ?
>>>
>>> Thank you.
>>> Mohamed
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20241218/094b6bfd/attachment.htm>