HTML Forms

The following are examples of HTML forms that can be used to send data through. Please note all user field names and values are case-sensitive by default.

The simplest case is a login of an existing user.
After the user submits the form to the UserRemoteLogin.aspx page, their browser is redirected to the Storefront website and the user is logged in:

<form method="post" action="http://www.test.com/UserRemoteLogin.aspx">   <input type="hidden" name="Username" value="kevin_m" />   <input type="hidden" name="Password" value="m_n1v3k" />   <input type="submit" value="Print Centre" /> </form>

In case of a failure, the Storefront log contains a record explaining the reason why it was not possible to log the user in.

If the Unique ID security check method is selected, then the minimum form looks like this:

<form method="post" action="http://www.test.com/UserRemoteLogin.aspx">   <input type="hidden" name="Username" value="kevin_m" />   <input type="hidden" name="Password" value="m_n1v3k" />   <input type="hidden" name="RemoteLoginUniqueID" value="RLkevin" />   <input type="submit" value="Print Centre" /> </form>

Note that the name of the RemoteLoginUniqueID parameter must match the one filled in the configuration field Unique ID Profile Field Name. The value must then match the one filled in the user’s Profile Field.
Any User Profile Field can serve as the Unique ID.
If both of the options Security Check - Unique ID and Create New Users If Not On System are selected, then a new user with the given details is created (if the user doesn’t already exist). In such a case it makes sense to provide more details about the user:

<form method="post" action="http://www.test.com/UserRemoteLogin.aspx">   <input type="hidden" name="Username" value="kevin_m" />   <input type="hidden" name="Password" value="m_n1v3k" />   <input type="hidden" name="RemoteLoginUniqueID" value="RLkevin" />   <input type="hidden" name="groups" value="Marketing,Accounts" />   <input type="hidden" name="UserProfileFirstName" value="Kevin" />   <input type="hidden" name="UserProfileLastName" value="Morgan" />   <input type="hidden" name="UserProfileEmailAddress" value="kevin.morgan@test.com" />   <input type="hidden" name="UserProfileAddress1" value="33 City Road" />   <input type="hidden" name="UserProfileCity" value="London" />   <input type="hidden" name="UserProfilePostalCode" value="EC1V 1LH" />   <input type="hidden" name="UserProfileCountry" value="GB" />   <input type="submit" value="Print Centre" /> </form>

The example above creates the new user kevin_m on the first attempt to log in.
Next time, kevin_m will be logged in, and if the option Update User Profile is switched on, the present User Profile Fields will be updated.
Let’s say the address information in the example above would appear as <input type=”text” /> on the page, then the user would be able to change their Profile Fields on each login.

The previous example creates new users only if Unique ID is the selected method of the Security Check, plus the Create New Users If Not On System option is active.
If the Default Security Check takes place, or the Create New Users option is off, then, in order to create a new user, the browser must send the request to the UserRemoteRegister.aspx page:

<form method="post" action="http://www.test.com/UserRemoteRegister.aspx">   <input type="hidden" name="Username" value="kevin_m" />   <input type="hidden" name="Password" value="m_n1v3k" />   <input type="hidden" name="groups" value="Marketing,Accounts" />   <input type="hidden" name="UserProfileFirstName" value="Kevin" />   <input type="hidden" name="UserProfileLastName" value="Morgan" />   <input type="hidden" name="UserProfileEmailAddress" value="kevin.morgan@test.com" />   <input type="hidden" name="UserProfileAddress1" value="33 City Road" />   <input type="hidden" name="UserProfileCity" value="London" />   <input type="hidden" name="UserProfilePostalCode" value="EC1V 1LH" />   <input type="hidden" name="UserProfileCountry" value="GB" />   <input type="submit" value="Print Centre" /> </form>

When calling UserRemoteRegister.aspx, every attempt to register an already existing user will fail.
The Storefront log will keep the record.

It may be desirable to specify a different landing page and/or the logout destination. A custom error page can also be specified, to which the user will be redirected in case of a failure:

<form method="post" action="http://www.test.com/UserRemoteLogin.aspx">   <input type="hidden" name="Username" value="kevin_m" />   <input type="hidden" name="Password" value="m_n1v3k" />   <input type="hidden" name="redir" value="UserContentShoppingCart.aspx" />   <input type="hidden" name="logoutUrl" value="http://www.roi360.co.uk" />   <input type="hidden" name="error" value="http://www.yoursite.com/PrintError.html" />   <input type="submit" value="Print Centre" /> </form>