Hi

I want to allow verfified registration to a portal, but first check to see if the email address given exists in a remote database so I can supply a choice to registrant. If the email exists, then it already has roles available so no dificulties. Checking the remote database isn't a problem as that is always done on login anyway through a decorator on the standard authentication module.

If the email address exists, just continue as normal. They will get the apropriate roles allocated from the remote db when they verify. This happens now.

If it doesn't exist, the user needs to agree that they expected that to be the case. If so, they continue with no additoinal roles other than authenticated. If not, it means they thought they had some roles (e.g. a membership status with the organisation) but their email address didn't reveal them. They need to either resubmit the registration with an alternate email address (maybe their company email instead of a private one) or allow a human to manually verify their rights to roles sometime in the next day by making the appropriate entry in the remote db.

Any suggestions on how to go about this? I don't really want to modify core dnn modules if at all possible, although I am able to do it if needed. I was wondering if the private/verified membership setting could be changed for this registration based on whether the email address exists in the remote database or not?

Thanks in advance

Neil