In the varied environments where the Profile Manager solution is installed, there may be an existing launcher application running on the device. This provides the customer with the ability to keep their existing launcher for the user sign-on process and then pass the user information to the Profile Client to authenticate with the Profile Manager.
The four tags used in this environment are:
Key_user_name
Key_user_pwd
Key_submit
Key_domain
The values entered in these tags identify the input fields to automate the login process. As an illustration, shown below is the actual html of a sample login screen:
<div class="input-row">
<table>
<tr>
<td>
<p> <label style="margin-top:-14px" for="username">Login ID:</label></p>
</td>
<td>
<span class="ctrl">
<input type="text" name="username" id="username" class="textinput" value=""/>
</span>
</td>
</tr>
</table>
</div>
<div class="input-row">
<table>
<tr>
<td>
<p> <label style="margin-top:-14px" for="password">Password:</label></p>
</td>
<td>
<span class="ctrl">
<input type="password" name="password" id="password" class="textinput"autocomplete="off"/>
</span>
</td>
</tr>
</table>
</div>
<div class="button-row">
<span class="ctrl">
<input type="submit" value="Login" id="submit" class="formButton"
onclick="this.disabled=true;document.body.style.cursor = 'wait';
this.className='formButton-disabled';form.submit();return false;"/>
