DSAPI filter no longer working

HCL Domino Domino Forum
1

After upgrading from R5.0.13 to R7.0.2 my authentication filter is no longer working.The code is the same as found in most filters I can find on the internet:

int HttpFilterProc(FilterContext* context, unsigned int eventType, void* eventData) {

	switch (eventType) 

	{

		case kFilterAuthenticate:

		case kFilterAuthUser:

			return Authenticate(context, (FilterAuthenticate*)eventData);

		default:

			return kFilterNotHandled;

	}

}

The following lines of code in Authenticate always returns because for some reason the authData->foundInCache is always true:

if (!authData || authData->foundInCache) {

	return kFilterNotHandled;

}

Does anybody know anything about changes that might affect the behaviour of the filters? Is this a config problem.

2

Subject: DSAPI filter no longer working

I tried writing a DSAPI filter for 6.0 and I have given up. I based my filter off of the same samples that you have seen.

If I had a “skeleton” filter, like the one you posted then it just worked fine for me. I then added some code to open a Notes DB. This caused the filter to lock up. I then took that code out and added some code to access an LDAP server. This code also locked up the http server.

When I created a sample program to run on my PC to access the database and to access the same LDAP server as in the filter, the code worked perfectly.

I have found that support and documentation for “home brew” DSAPI filters is sparse at best.

Good luck.