Register option within Login

[petersioufi]

We configure local users manually but would like to allow external users to either login (if they already have a profile/password) or Register for a new user profile. This is like "sign in" or "sign up" in the login page. We would program the backend to accept requested login details (email address and name) then the back end would send them login details after approval.

My question is about the best way to do that so that we do not disturb the progressive Valence Update process. Would it be in the Hook and how would we change the login page to contain extra details when the "sign up" button is pushed. We already know how to configure new users in the back end so this is only a front end question, apart from how to call a back end program before actual login (i.e. before SID is assigned).

Thanks,

Peter.

[Johnny Major]

So, you would like to add another button to the login screen—where it asks for a username and password—labeled 'Sign Up'?

[petersioufi]

Hi Johnny,

Yes, we found that adding a button to HOOK works great and we can pop up a window to accept some more info for self-registration. Now we're trying to work out how to call back end API because we can't use VVCALL prior to login, so we're exploring web service to handle capturing login registration data. Unless we can use VVPORT, but that looks like it's locked.

Peter

[Johnny Major]

I would just add a web service via Portal Admin; however, you could always add the program alias directly to the Apache config for that instance.

[petersioufi]

Hi Johnny,

Something above the hook is adding "sid" and "lang" to our web service call. We tried using vanilla java and EXT JS. The sid is being set to "undefined" which causes our web service to return an error as follows:

{
"success": false,
"hdr": "invalidSession",
"body": "sessionInvalid",
"vvid": 529,
"action": "LOGOUT"
}?

From a simple browser, however, it works perfectly!

Peter

[Johnny Major]

Hi Peter,

Valence, by default, auto-applies information like session ID to make it easier; however, there are situations where you don't want that to happen, like in your case. You can add the parameter _omit_all_remove_ with the value of true, and it will not apply that information.

Thanks?