cancel
Showing results for 
Search instead for 
Did you mean: 

Weird issue with HANA XS SAML SSO and Odata service

robert_camangon
Explorer
0 Kudos

We recently updated to SAP HANA 2.0 SPS01 and we have a weird issue with HANA XS SAML SSO and Odata service after the update. We use ADFS as the IDP for our SAML. Here is a brief of the issue.

1) Accessing url "https://<server>:<port>/OData_Services/<odata_name>/services.xsodata/Organizations?$filter=indexof(tolower(ORGNAME),'town') ge 0&$top=50" will show error “No cookie with target path found in request” which suggests that SAML Token is not passed. There is nothing in the indexserver or xsserver logs to suggest an issue though.

2) Accessing url "https://<server>:<port>/OData_Services/<odata_name>/services.xsodata" which is the same as the url in ITEM 1 without filters works and user is authenticated. After getting authenticated, trying the url in ITEM 1 will work without issues.

3) Open a new session and access url "https://<server>:<port>/OData_Services/<odata_name>/services.xsodata/Organizations?$filter=ORGNAME%20eq%20%27AB%20Transportation%27". This is also the same as in ITEM 1 but with a filter EQ. This works without issues as well and user is authenticated. After getting authenticated, trying the url in ITEM 1 will work without issues.

The thing is the application consuming the data needs to have a filter that is not exact as users will use that application to query data. Also, as it works after getting authenticated from another url, this is very weird.

Tried with SAP but no dice as they seem to not know why this is happening. Does anyone have an idea as to where to check or how to fix it?

Any ideas or leads are more than welcome as I'm now on my wits end with this issue.

Thanks a lot.

Accepted Solutions (1)

Accepted Solutions (1)

robert_camangon
Explorer

Hi Lutz,

Apologies for the late reply. Anyway, SAP has come back on this and verified that this is an issue related to the temp fix we had before for a bug (using parameter ce2qo_disable_unfolding). After update to the newer patch, the patch should have taken care of the bug so the temp fix before should be turned off. After doing that, it worked without issues.

Regards,

Robert

Answers (1)

Answers (1)

LutzR
Active Contributor
0 Kudos

Hi Robert, just a quick guess:

Did you already try to properly urlencode your filter parameter? Your query string violates standards.

Instead of

https://<server>:<port>/OData_Services/<odata_name>/services.xsodata/Organizations?$filter=indexof(tolower(ORGNAME),'town') ge 0&$top=50

try

https://<server>:<port>/OData_Services/<odata_name>/services.xsodata/Organizations?$filter=indexof%2...

Some HANA software component might stumble over ( or ' or spaces.

Cheers, Lutz