Home » discuss » Public forums » Developing for iMIS

ValidateUser from AsiMembership Provider returns null reference

Posted August 4th, 2009 by markpaulsolomon
| |

I have the iMIS AsiMembershipProvider to a Sharepoint site as the default membership provider and it creates users correctly (as long as I provide it with a valid providerKey for an existing iMIS contact). However, it crashes with a cryptic null; reference exception when trying to validate.

As a work around, I inherited the AsiMembershipProvider and overrode the "ValidateUser" method by redirecting to the iMIS SOA membership web service "ValidateUser". This works and I can now log in. However, I would rather not add this service to my system architecture if I can help it. Why would the web service work when the AsiMembershipProvider doesn't.

It should be noted that  the provider is running on a different app server than the web service. Are the 2 methods looking for some system setting or something that may be present on my iMIS web server but not on my Sharepoint server machine? Or alternatively, is the AsiMembershipProvidert tryping to do something altogether different? One thing that came to mind is encryption, since passwords are invovled. Does the provider expect encryption configuration somewhere?

Any help would be greatly appraciated!

‹ Is there a way to auto-login the iMIS 15 Public ViewEvent registration, without payment ›
login or register to post comments | printer friendly version

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Can you post the entire

On August 4th, 2009 Eric Means says:

Can you post the entire error message, including the stack trace?

login or register to post comments

Not right away

On August 4th, 2009 markpaulsolomon says:

Thanks for the response but I cant do this right away as the code has been recomp[iled and put into the ingreation environment with the SOA code. However, I can tell you that the error is the classic null reference exception and the stack trace ends at the membershipprovider.validateuser call. There is no other calls after that on the stack trace. I will try to recreate the error soon and post more information.

login or register to post comments