All -
While debugging another issue, I found that during the results authorization process we are receiving a errnum 16 on the first document in our result set (found in the resauthdebug.log).
I believe this is due to the fact that when accessing the first document in the result set, it is performing several redirects while it resolves the authentication through our SSO application. It appears that after 5 redirects, the result fails with errnum 16.
Subsequent documents in our result set seem to work fine, it's just the first one every time we perform a search or page through the results.
Can you confirm that this is accurate? If so, is there a way that we can configure this setting for this particular profile?
Thanks in Advance,
Russell
While debugging another issue, I found that during the results authorization process we are receiving a errnum 16 on the first document in our result set (found in the resauthdebug.log).
I believe this is due to the fact that when accessing the first document in the result set, it is performing several redirects while it resolves the authentication through our SSO application. It appears that after 5 redirects, the result fails with errnum 16.
Subsequent documents in our result set seem to work fine, it's just the first one every time we perform a search or page through the results.
Can you confirm that this is accurate? If so, is there a way that we can configure this setting for this particular profile?
Thanks in Advance,
Russell