Registration and auto-login issue

JonP

I've got a multi-tenant saas where I have the registrant use guest access, which pulls up the Guest VP and the following process runs:

ENTER NEW LoginRegistration USING Main
LoginRegistration.URL='https://cm.plantain.io/app/logonOp.aw?e='+ENCRYPT_B64('domain=Plantain&userName='+LoginRegistration.Username+'&password='+LoginRegistration.Pass+'&testingMode=false&perspective=TopMenu&dynamic=True')
...
[Bunch of BOs are created and welcome email sent]
...
DISPLAY URL LoginRegistration.URL FULL SCREEN

When it auto-logs the registrant in with DISPLAY URL, the following error occurs: "This operation is available for registered users only..."

If I permit guest access for that operation, it runs, but then I have the same issue with the next operation, so the problem is that the registrant still has guest access even though the registrant was assigned a different access level during registration.

Also, if I try to login as that user, I get "invalid credentials". I'm using a BO called Person that's a member of SystemUser with the username being the email address. I'm setting AccessLevel to "Admin" which is almost wide open. The CREATE action that's part of the above process looks like this:

CREATE Person WITH Person.Name=LoginRegistration.Name,Person.EmailAddress=LoginRegistration.Username,Person.LoginName=LoginRegistration.Username,Person.Password=LoginRegistration.Pass,Person.Foundation='Responsible',Person.AccessLevel='Admin',Person.License='Yes',Person.Account=ThisAccount,Person.Role=ThisRole

Anything jump out?

customaware

Not sure what you are doing with the URL Jon.

WHy not just use Aware’s built in ‘Registration’ type form?

JonP

Sorry, I didn't provide enough information.

I have a NP BO, LoginRegistration, that collects attributes for two BOs, Person (member of SystemUser) and Account (for managing licenses). That way the registrant doesn't have to fill out two different forms. Only the name of the account and phone # is needed for the Account BO, so it would be annoying for a registrant to have to fill out a separate form for that.

Besides creating the Account and Person instances, I auto-create some other BO instances that the registrant would find useful, then send an email, then auto-login the registrant so they don't have to bother with logging in after registering. That's what the URL is for.

What does the built-in form do that I can't do otherwise?

tford

I'm not clear on all your steps, Jon, but It's pretty standard practice when you register for a new account online, you receive an email with a link to log into your newly created account to verify that the email address is correct.

Are you saying that you bypass this step, Jon?

JonP

That's a good point. I should do that. That might also address my password issue if I assign them a temp password when they register and have them change it when they first login.